[fpc-pascal] A warning when Blockwriting/reading dynamic array pointers

J├╝rgen Hestermann juergen.hestermann at gmx.de
Sat Apr 2 19:36:34 CEST 2011


Jonas Maebe schrieb:
 > If you don't want the compiler to interfere with anything you do, do 
not use automated types such as ansistring, unicodestring, dynamic array 
and COM-style interfaces. The whole point of these types is that the 
compiler will do lots of stuff behind your back, because without that 
the reference counting cannot work.

You are missing the whole point: It is just the problem that some 
("automated"?) data types are not fully documented! How do I know which 
type behaves how? Do I have to guess it (as I did now)? You are always 
saying that you cannot do this and that with these and other types but 
there is no clear documentation what exactly you can do and what you can 
*not* do and what the compiler does in the background.

If all this knowledge would be visible *before* trapping into the 
pitfalls (after painful debug sessions) then the power of these types 
could be very useful. But now it is blind flying.




More information about the fpc-pascal mailing list