public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giecrilj at stegny dot 2a.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51540] doxygen documentation for partial_sum misleading
Date: Fri, 16 Dec 2011 20:33:00 -0000	[thread overview]
Message-ID: <bug-51540-4-1xKX8GAFa1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51540-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Christopher Yeleighton <giecrilj at stegny dot 2a.pl> 2011-12-16 20:31:24 UTC ---
I would rather prefer to be able to use gcc (as a software developer) while not
having the ISO standard, which is 1) unreadable with an unarmed eye, 2) not
free (as in anything), 3) not bundled (of course), 4) written by and for
compiler manufacturers.  I understand there is no documentation for the
language itself, but that is (more or less) easily taught; however, requiring
the developer to know all the (essential) details of the standard library by
heart is a bit too much for me.  So I have taken the liberty of pointing out
this little inconvenience and I am trying to use the transform algorithm
instead.


  parent reply	other threads:[~2011-12-16 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 23:07 [Bug libstdc++/51540] New: partial_sum (int *, int *, int *, multiplies < int >) does not use operator +(complex, complex) giecrilj at stegny dot 2a.pl
2011-12-14  0:06 ` [Bug libstdc++/51540] " redi at gcc dot gnu.org
2011-12-14  0:30 ` redi at gcc dot gnu.org
2011-12-14  7:16 ` giecrilj at stegny dot 2a.pl
2011-12-14  9:39 ` paolo.carlini at oracle dot com
2011-12-14 10:26 ` giecrilj at stegny dot 2a.pl
2011-12-14 10:59 ` paolo.carlini at oracle dot com
2011-12-14 11:05 ` redi at gcc dot gnu.org
2011-12-14 11:18 ` [Bug libstdc++/51540] doxygen documentation for partial_sum misleading redi at gcc dot gnu.org
2011-12-14 11:19 ` paolo.carlini at oracle dot com
2011-12-15  9:53 ` redi at gcc dot gnu.org
2011-12-15  9:56 ` redi at gcc dot gnu.org
2011-12-16 19:14 ` giecrilj at stegny dot 2a.pl
2011-12-16 20:17 ` paolo.carlini at oracle dot com
2011-12-16 20:33 ` giecrilj at stegny dot 2a.pl [this message]
2011-12-17 13:26 ` redi at gcc dot gnu.org
2011-12-17 13:33 ` redi at gcc dot gnu.org
2011-12-17 17:55 ` giecrilj at stegny dot 2a.pl
2011-12-18 22:35 ` redi at gcc dot gnu.org
2011-12-18 23:31 ` redi 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-51540-4-1xKX8GAFa1@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).