public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46513] Request: Warning for use of unsafe string handling functions
Date: Wed, 17 Nov 2010 01:25:00 -0000	[thread overview]
Message-ID: <bug-46513-4-i6YT1P0gE6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46513-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46513

--- Comment #2 from Jeffrey Walton <noloader at gmail dot com> 2010-11-17 01:08:22 UTC ---
Hi Jonathan,

(In reply to comment #1)
> The maintainers of GNU libc, the C and C++ committees and the POSIX working
> group have not seen fit to include those functions, and they're not available
> on my GNU/Linux box.
Interesting. In 2010, I was hoping the strl* functions would side step the
political mess of TR24731-1 on *nix. For those resisting, TR24731-1 is now a
normative part of the C1x draft (as Annex K), so its coming whether they want
it or not :/

Never the less, a warning would still be useful since lots of code still
employs the unsafe functions. For those who are inclined - such as myself and
others who perform security related audits - a compiler warning would be a
welcome addition, even if there is no standard replacement. I'll tackle "what
to replace it with" in-turn on the specific platform.

Jeff


  parent reply	other threads:[~2010-11-17  1:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  0:53 [Bug c++/46513] New: " noloader at gmail dot com
2010-11-17  1:08 ` [Bug c++/46513] " redi at gcc dot gnu.org
2010-11-17  1:25 ` noloader at gmail dot com [this message]
2010-11-17  3:21 ` noloader at gmail dot com
2010-11-17  5:40 ` noloader at gmail dot com
2010-11-17 10:47 ` redi at gcc dot gnu.org
2010-11-17 11:51 ` joseph at codesourcery dot com
2020-05-19 20:40 ` msebor at gcc dot gnu.org

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-46513-4-i6YT1P0gE6@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).