[fpc-devel] Alternative parsers

[Helmut Hartl]

  Am 19.10.10 15:40, schrieb Alexander Klenin:
> I fully understand that the reason for degrading the code structure
> was efficiency.
> I just doubt that it was/is a good trade-off.
Dear FPC Team,

After finishing porting the bullet physics library from C++ to FPC in the
last 2 months (http://bulletphysics.org/wordpress/). I had the chance
to compare Xcode, MS Visual C++  and MinGW GCC regarding compilation
speed.
FPC is about 3-20 times(!) faster then those (modern) compilers on pure
compilation speed. That is a fact at least for me and my employees.
I had to debug the library on multiple archs with multipe tools side by 
side,
step by step to find my porting errors - and I had to
add lots of debug code in the original code, so I was able to "feel" and
measure the turn around times.

I am happy that you all have a deep understanding of writing fast and
memory efficient code, because I can use the compiler as spell checker.

I am happy that I can use FPC to do 10 GBit Line speed network analysis and
real time protocol identification under FreeBSD, with a small team of
developers because they can read and debug pascal code fast and have 
superior
turn around times.

I am happy that I can also use "degraded" datastructures in conjunctions 
with
lock free algorithms and that I have the choice to use them if I 
understand them.

Thank you all for the exceptional stability of the FPC trunk on Windows, 
FreeBSD (32)
and OSX because we use the latest trunk version to do our development 
(generics).

Thank you that my company was/is able to write a cross platform OpenGL 
Engine
for data visualization which now works with OpenGL 4, OpenCL and optimized
Shadercode, completly driven by FPC. (Shadercode and OpenCL code is in C)
Proving that FPC is able to feature recent technology projects.

Thank you for your long time support of language features - using 
objects (TP objects)
as generics has proven to be sucessfully fast for vector, 
matrix,quaternion and memory
management operations while maintaining a FPU needed layout easily.

Thank you all for your time reading, thinking, answering often 
stupid/lazy mails and
bug reports from me.

Please continue your good judgement about trunk codebase improvements.

helmut