> one big problem with this sort of thing is that you can pass anything to an > untyped const parameter *INCLUDING* a pointer, so if you change something > from taking an untyped pointer to taking an untyped const parameter you are > going to cause strange bugs for users. >
I'm not saying that you should add this, only add if it's in one version of the unit AND you feel compat. is important. I'm not particularly happy with "pascalization" of direct interfaces myself. Ales _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
