From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] why the leading under score added to function names?
Date: Thu, 23 Feb 2012 15:30:21 +1100 [thread overview]
Message-ID: <20120223043021.GA72269@dereel.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1202230752140.62608@aneurin.horsfall.org>
On Thursday, 23 February 2012 at 8:22:17 +1100, Dave Horsfall wrote:
> On Wed, 22 Feb 2012, arnold at skeeve.com wrote:
>> It also shows the consequences a small, apparently local decision
>> can have: here we are 40+ years later and GCC on Windows is still
>> preprending underscores to function names!
>
> When it comes to Windoze, nothing surprises me any more. Unix has
> evolved over the years, but Windoze was spat out and hatched.
I'm no friend of Microsoft either, but gcc isn't exactly Microsoft.
What Arnold mentions here is Unix history in action.
Greg
--
Sent from my desktop computer
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20120223/bb41d2c1/attachment.sig>
next prev parent reply other threads:[~2012-02-23 4:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 19:17 arnold
2012-02-22 21:22 ` Dave Horsfall
2012-02-22 22:47 ` A. P. Garcia
2012-02-23 4:30 ` Greg 'groggy' Lehey [this message]
2012-02-25 18:45 ` Random832
2012-02-25 19:24 ` Steve Nickolas
2012-02-25 20:39 ` John Cowan
2012-02-25 22:15 ` Random832
2012-02-26 13:28 ` Ronald Natalie
2012-02-27 1:30 ` random832
-- strict thread matches above, loose matches on Subject: below --
2012-02-20 20:52 arnold
2012-02-20 23:21 ` Dave Horsfall
2012-02-21 0:34 ` Brantley Coile
2012-02-21 2:50 ` Warner Losh
2012-02-21 3:33 ` John Cowan
2012-02-21 3:41 ` Steve Nickolas
2012-02-21 18:18 ` ron
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=20120223043021.GA72269@dereel.lemis.com \
--to=grog@lemis.com \
/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).