From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] go forth and ulong no more!
Date: Thu, 22 Nov 2012 12:35:42 +1100 [thread overview]
Message-ID: <CAJQxxwkMD4cmj5TCTVZP+Lug+Sf3aDhvHeUTYz0d2AHou0ocFw@mail.gmail.com> (raw)
In-Reply-To: <db8d12d394c6aa34f8f4c758ef2e98ab@kw.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
i think that go's scalar types would work better. also usize is a bit
dicky.
brucee
On Nov 22, 2012 12:23 PM, "erik quanstrom" <quanstro@quanstro.net> wrote:
> On Wed Nov 21 19:19:21 EST 2012, benavento@gmail.com wrote:
> > hola,
> >
> > usize, really?
> >
> > any reason not use this opportunity to join the world and use inttypes.h
> or stdint.h format?
>
> have you read the opengroup pubs?
>
>
> http://pubs.opengroup.org/onlinepubs/007904975/basedefs/stdint.h.html
>
> http://pubs.opengroup.org/onlinepubs/009604599/basedefs/inttypes.h.html
>
> i don't see any advantage to using whatever types these guys are using.
> when porting things from plan 9, it's good to have different type names.
> the assumptions of various systems differ. when porting things to plan 9,
> you're likely going to be using ape anyway.
>
> these headers are missing a type representing physical memory, and Rune.
> no, i'm never going to consider using wchar_t instead.
>
> yet they have types we do not want such as int_{least,fast} and int_max_t.
> they seem to be a trap set by greybeards for unsuspecting young
> programmers.
> one could hold this kind of thing up as a reason that c is an old and
> broken language.
>
> and then there's the printf macros. oh, joy.
>
> i'm sure that others could back this up with more inteligent reasoning.
> i'm just
> prone to rant (had you noticed) when i see some of this stuff.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 2077 bytes --]
next prev parent reply other threads:[~2012-11-22 1:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 21:49 erik quanstrom
2012-11-22 0:18 ` Federico G. Benavento
2012-11-22 1:21 ` erik quanstrom
2012-11-22 1:35 ` Bruce Ellis [this message]
2012-11-22 2:08 ` Dan Cross
2012-11-22 2:15 ` Bruce Ellis
2012-11-22 2:33 ` Charles Forsyth
2012-11-22 2:35 ` Charles Forsyth
2012-11-22 3:44 ` Bruce Ellis
2012-11-22 8:56 ` Charles Forsyth
2012-11-22 9:02 ` Charles Forsyth
2012-11-22 10:21 ` erik quanstrom
2012-11-22 11:00 ` Richard Miller
2012-11-22 11:11 ` Charles Forsyth
2012-11-22 11:13 ` Charles Forsyth
2012-11-22 11:32 ` Richard Miller
2012-11-22 11:38 ` Charles Forsyth
2012-11-22 11:49 ` erik quanstrom
2012-11-22 13:26 ` Richard Miller
2012-11-22 14:05 ` Charles Forsyth
2012-11-22 14:53 ` erik quanstrom
2012-11-22 11:50 ` erik quanstrom
2012-11-22 11:10 ` Richard Miller
2012-11-22 11:13 ` Charles Forsyth
2012-11-22 11:32 ` Charles Forsyth
2012-11-22 11:33 ` Charles Forsyth
2012-11-22 10:31 ` Charles Forsyth
2012-11-22 12:39 ` Anthony Martin
2012-11-22 12:48 ` Charles Forsyth
2012-11-22 12:50 ` Charles Forsyth
2012-11-22 12:54 ` Anthony Martin
2012-11-22 13:08 ` Charles Forsyth
2012-11-22 9:59 ` Charles Forsyth
2012-11-22 9:38 ` Charles Forsyth
2012-11-22 9:40 ` Charles Forsyth
2012-11-22 18:18 ` Federico G. Benavento
2012-11-22 11:36 Richard Miller
2012-11-22 11:45 ` Charles Forsyth
2012-11-22 11:54 ` Steve Simon
2012-11-22 11:59 ` Charles Forsyth
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=CAJQxxwkMD4cmj5TCTVZP+Lug+Sf3aDhvHeUTYz0d2AHou0ocFw@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.net \
/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).