9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Is this a bug in 8c?
Date: Fri, 15 Mar 2002 08:51:56 -0500	[thread overview]
Message-ID: <f8a6bc20b1d3d559ec2fa7364b23ec46@plan9.bell-labs.com> (raw)

> long long is an "integer type" according to the meaning
> of that term in the C standard. 
....
> ... snide self-superiority ...
> 8c is apparently
> riddled with *intentional* bugs. 

Just a minute here.  I'm not apologizing for long long not supporting
?:, because I think it really should, but nonetheless:

a) long long is not an integer type according to the ANSI C standard I
hold in my hand.  Perhaps it is in C9X, but it's not even mentioned in
the old standard.  It isn't a type at all as far as the standard is
concerned.  I know other compilers came to implement it, but where in
the 1989 standard - the one 8c was written to - does it mention long
long?

b) 8c is not "riddled" with "intentional bugs".  Be careful who you
call snide and self-superior.  I think the strongest honest statement
you could make as far as long long is concerned is that some of the
operations on the long long extension are unimplemented.  That is a
far cry from "riddled" with "intentional bugs".

-rob



             reply	other threads:[~2002-03-15 13:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 13:51 rob pike [this message]
2002-03-15 17:26 ` Thomas Bushnell, BSG
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 16:41 Fco.J.Ballesteros
2002-03-15 14:43 bwc
2002-03-15 14:11 Russ Cox
2002-03-15 14:08 Russ Cox
2002-03-15 11:52 forsyth
2002-03-15 16:53 ` Thomas Bushnell, BSG
2002-03-15 17:53   ` William Josephson
2002-03-15 11:52 forsyth
2002-03-14 19:43 Russ Cox
2002-03-14 19:49 ` Martin Harriss
2002-03-15 10:18 ` Thomas Bushnell, BSG
2002-03-15 10:19 ` Douglas A. Gwyn
2002-03-14 19:20 bwc

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=f8a6bc20b1d3d559ec2fa7364b23ec46@plan9.bell-labs.com \
    --to=rob@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).