From: Charles Forsyth <charles.forsyth@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:48:54 +0000 [thread overview]
Message-ID: <CAOw7k5hk1zw0mFv7=74nWMh=V-X5_KRjtE07QLAkWnkK1Jo7GQ@mail.gmail.com> (raw)
In-Reply-To: <20121122123850.GA8106@dinah>
this is just a sample, but there were other likely candidates:
./src/pkg/runtime/cpuprof.c: uintptr count;
./src/pkg/runtime/cpuprof.c: uintptr count; // tick count
./src/pkg/runtime/cpuprof.c: uintptr evicts; // eviction count
./src/pkg/runtime/cpuprof.c: uintptr lost; // lost ticks that need to be logged
./src/pkg/runtime/cpuprof.c: uintptr totallost; // total lost ticks
./src/pkg/runtime/zmprof_386.c:uintptr allocs;
./src/pkg/runtime/zmprof_386.c:uintptr frees;
./src/pkg/runtime/zmprof_386.c:uintptr alloc_bytes;
./src/pkg/runtime/zmprof_386.c:uintptr free_bytes;
./src/pkg/runtime/zmprof_386.c:uintptr recent_allocs;
./src/pkg/runtime/zmprof_386.c:uintptr recent_frees;
./src/pkg/runtime/zmprof_386.c:uintptr recent_alloc_bytes;
./src/pkg/runtime/zmprof_386.c:uintptr recent_free_bytes;
./src/pkg/runtime/zmprof_386.c:uintptr hash;
./src/pkg/runtime/zmprof_386.c:uintptr nstk;
./src/pkg/runtime/runtime.h: uintptr n; // number of parameters
./src/pkg/runtime/thread_netbsd.c: uintptr nout;
./src/pkg/runtime/cpuprof.c: uintptr nlog;
On 22 November 2012 12:39, Anthony Martin <ality@pbrane.org> wrote:
> Charles Forsyth <charles.forsyth@gmail.com> once said:
>> On 22 November 2012 03:44, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>> > uintptr in all over the go packages because it is right.
>>
>> I hadn't noticed that particularly, but having grep'd the source, I
>> see it's also used for variables that are counters and numbers of
>> things.
>
> Can you give an example? Nothing jumped out after a quick glance.
>
>> Is that right too? I suspect it's more out of expediency. Some other
>> type usage looks odd too. int32 where int would do. Curious.
>
> Such as? The only one I can think of is (*os.File).Fd returning
> a uintptr but that was changed from int for a reason (Windows).
>
> Cheers,
> Anthony
>
>
next prev parent reply other threads:[~2012-11-22 12:48 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
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 [this message]
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='CAOw7k5hk1zw0mFv7=74nWMh=V-X5_KRjtE07QLAkWnkK1Jo7GQ@mail.gmail.com' \
--to=charles.forsyth@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).