From: Brantley Coile <bwc@borf.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "ridiculous benchmarks"-r-us
Date: Fri, 9 Jan 2004 13:52:55 -0500 [thread overview]
Message-ID: <4c36397125ce19a96ba073306ca1ef5e@borf.com> (raw)
In-Reply-To: <slrnbvtrgl.h6p.usenet@icarus.freeuk.com>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
What possible rationale did they have for adding nested procedures to C?
Did they call them mid-functions in the standard? Why rename a concept
just because it's 47 years old!
Brantley
[-- Attachment #2: Type: message/rfc822, Size: 2326 bytes --]
From: Icarus Sparry <usenet@icarus.freeuk.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "ridiculous benchmarks"-r-us
Date: Fri, 9 Jan 2004 18:19:11 GMT
Message-ID: <slrnbvtrgl.h6p.usenet@icarus.freeuk.com>
On 2004-01-09, mirtchov@cpsc.ucalgary.ca <mirtchov@cpsc.ucalgary.ca> wrote:
> It took me much longer -- until I looked at their "C" code (term used
> very loosely) trying to compile it on Plan 9... There are multiple
> gems in it including ++ on a double, mid-function variable definitions
> (C-code, right?)
C99 added mid-function variable definitions.
next prev parent reply other threads:[~2004-01-09 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 17:42 mirtchov
2004-01-09 17:47 ` ron minnich
2004-01-09 18:19 ` Icarus Sparry
2004-01-09 18:37 ` mirtchov
2004-01-09 20:25 ` Sam
2004-01-09 20:29 ` Charles Forsyth
2004-01-09 20:44 ` Sam
2004-01-09 20:44 ` Brantley Coile
2004-01-10 0:37 ` Dennis Ritchie
2004-01-09 20:48 ` mirtchov
2004-01-11 1:02 ` [9fans] 'ridiculous benchmarks'-r-us Joel Salomon
2004-01-09 18:52 ` Brantley Coile [this message]
2004-01-09 20:06 ` [9fans] "ridiculous benchmarks"-r-us Tristan Seligmann
2004-01-10 5:06 ` boyd, rounin
2004-01-09 19:40 ` Roman Shaposhnick
2004-01-09 20:54 ` Atanas Bachvaroff
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=4c36397125ce19a96ba073306ca1ef5e@borf.com \
--to=bwc@borf.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).