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 <[email protected]> wrote: > Charles Forsyth <[email protected]> once said: >> On 22 November 2012 03:44, Bruce Ellis <[email protected]> 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 > >
