Re: [fpc-devel] Light weight threads for FPC

2007-12-14 Thread Eric Grange
> What do you mean by "light weight threads" ? How can it get "lighter" than TThread, >that offers close to no built-in "comfort"-functionality ? TThread (and BeginThread) are quite heavy for small tasks, not because of the Pascal code, but because of the OS overhead involved in creating, star

Re: [fpc-devel] Modernising Pascal

2005-02-25 Thread Eric Grange
1. This is not "entirely true" (the cost is at best logarithmic on the number of objects or your allocator has terrible fragmentation) Not really, you can use a memory map and achieve much lower fragmentation than classic memory managers (cf. "FastMM" submissions in the FastCode project in the b.

Re: [fpc-devel] Modernising Pascal

2005-02-25 Thread Eric Grange
This is simply not true. If you don't belive then check the following: 1. Look with google for Quake rewrittiend into .Net (i.e. GC stuff) -- surprise surprise -- difference is neglibile (<20%), Though if you study more what they compare, you'll find that their .Net version is actually running at

Re: [fpc-devel]Having FPC linker errors saved to a file

2004-01-08 Thread Eric Grange
Under dos I believe &> is used to pipe both stderr and stdout to file, under unix it is >&. Thanks :) Starting on that I found the DOS syntax: "2>". I'll probably use another approach than redirection to file in the end, to allow some more "interactive" compilation progress report. Eric

[fpc-devel]Having FPC linker errors saved to a file

2004-01-08 Thread Eric Grange
Is there a way to have the linker errors saved to a file (under Win32, 1.9.1) instead of just listed in the DOS box? The -Fe catches compilation errors and messages, but linker issues (such "undefined reference to SomeSymbol") are listed only in the DOS Box. I've tried to redirect output to a file

Re: [fpc-devel]Bunch'o questions for the new year

2004-01-07 Thread Eric Grange
It would be very nice to have a test case, yes. Submitted. Could remove objects, OpenGL references and all unit dependencies, besides "offending" code, only fat const arrays remain (a soup of indices...). Test proggy checks only one of the values, though at least 3/4 of them are "visually" incorrec

Re: [fpc-devel]Bunch'o questions for the new year

2004-01-07 Thread Eric Grange
Thanks Marco & Daniel (grouped reply and new question). I'm no expert on this, but afaik FPC generates stabs debug format, like gcc does. By simply compiling with -gl and -a you can see the debug info in the generated assembler (.s) file. Ok, I've quickly looked at lineinfo.pp, should be possible

[fpc-devel]Bunch'o questions for the new year

2004-01-01 Thread Eric Grange
First, Happy New Year! I've started investigating FPC support for GLScene (http://glscene.org), and have encountered a few issues: 1)are there any instruction on building FreePascal? I've got the CVS sources, tried several makefiles and .bat, browsed the READMEs, but couldn't get a compile to