public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95081] Copyright infringement by ROS2
Date: Tue, 12 May 2020 14:43:34 +0000 [thread overview]
Message-ID: <bug-95081-4-C8WJQUcGBx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95081-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95081
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|WAITING |RESOLVED
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Parameter names are not copyrightable. If you want to define a class with the
same API as std::vector then of course you're going to use the same names for
the member functions.
The only thing copyrightable in there are the comments. I suggest you bring
this up with the ROS2 project, or the Free Software Foundation. There's no GCC
bug here.
See https://www.gnu.org/licenses/gpl-violation.en.html
prev parent reply other threads:[~2020-05-12 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 11:27 [Bug c++/95081] New: " pacoarjonilla at yahoo dot es
2020-05-12 11:34 ` [Bug c++/95081] " redi at gcc dot gnu.org
2020-05-12 11:46 ` pacoarjonilla at yahoo dot es
2020-05-12 14:43 ` redi at gcc dot gnu.org [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-95081-4-C8WJQUcGBx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).