Helmut Eller :
> > If nobody bothers with even
> > considering the question, it would appear that it is not all that
> > important...
>
> Maybe nobody bothers because using clang is easier than to fight with
> FSF policies.
<>
It is never a good idea to exclude political and social ramifications
I told you I couldn't even vreate an accouny...and bugzilla is no a well
designed tool anyway
On Sat, May 28, 2011 at 04:25:37PM +0100, Jonathan Wakely wrote:
> On 11 May 2011 15:05, Jonathan Wakely wrote:
> >
> > Also, Bugzilla mails to the gcc-bugs list seem to be very slow at the
> > moment, t
FWIW
Array( const Array&rhs );
On Fri, Jun 10, 2011 at 08:30:05PM -0700, eric wrote:
> Dear Mr. Bjarne Stroustrup:
>
> Thanks your suggestion, I follow it but it show fatal error:Array.cpp:
> no such file
> so
> I add #include "Array.cpp" in my main program, pg52.cpp
> then
> it can compile
On Fri, Jul 15, 2011 at 09:07:46PM -0600, selma leathem wrote:
> -- Forwarded message --
> From: selma leathem
> Date: Fri, Jul 15, 2011 at 8:50 PM
> Subject: Interested In Doing Documentation Project
> To: gcc@gcc.gnu.org
>
> Hello,
>
> I am interested in doing the front end doc
On Tue, Dec 06, 2011 at 09:29:30AM -0500, Robert Dewar wrote:
> On 12/6/2011 9:16 AM, David Brown wrote:
>
> >I would say it's better to have false positives in cases like this, than
> >false negatives, because there are easy ways to remove the false
> >positives.
>
> My view is that for compiler
On 01/01/2012 12:42 AM, Robert Dewar wrote:
On 12/31/2011 4:44 AM, R A wrote:
alright, here's another example why eval is a good idea:
#define A 17
#define B 153
#define N1 ((A + B)/2) /* intended was (17 + 153)/2 */
#undef A
#define A 230
#define N2
On Fri, Nov 23, 2012 at 12:12:17PM -0800, Andrew Pinski wrote:
> On Fri, Nov 23, 2012 at 11:53 AM, Diego Novillo wrote:
> > In this day and age of rich-text capable mailers, restricting postings
> > to be text-only seems quaint and antiquated. Are there any hard
> > requirements that force us to
> >
> > incorrect accessment
>
> I can't parse this.
Maybe HTML markup can help you.
Stupid conversation
Why are you using google for your mail? Can't you get a real mail
client and a real mail access? Or maybe you work for google, in which
I can undersand it.
On Fri, Nov 23, 2012 at 03:35:57PM -0500, Diego Novillo wrote:
> On Fri, Nov 23, 2012 at 3:31 PM, Ruben Safir wrote:
> >> >
> >> > incorrect accessment
> >>
> >> I can't parse this.
> >
> >
> > Maybe HTML markup can help you.
&g
On Sat, Nov 24, 2012 at 12:58:33PM -0500, Daniel Berlin wrote:
> On Sat, Nov 24, 2012 at 12:13 PM, Ian Lance Taylor wrote:
> > Diego Novillo writes:
> >
> >> Sure. First I wanted to find out whether this requirement is just a
> >> technical limitation with our mailing list software.
> >
> > It i
>
> Yes, we should expect users to change, instead of keeping up with users.
No - we shouldn't punish developers by making them use stupid mime
translational servces that breaks the replying mechanism in EMACS and
mutt because they are stupidly try to post to a tech mailing list on
their androi
Sorry -
I wasn't really interested in debating this any more than one should
debate the effects of having your head squashed if you hang your head
over the rail when the IRT is coming.
It just gets squashed.
BTW, as well as learning to use text for email, also please learn to
trim the CC list..
On Sun, Nov 25, 2012 at 10:28:39AM -0500, Diego Novillo wrote:
> My main concern is losing valid content because of this limitation.
>
Your only concern is to send email with your android gmail.
You also need to learn to trim the CC line
14 matches
Mail list logo
