On Saturday 14 July 2012 14:07:30 Jonas Maebe wrote: > > > Hmm, up to now I listed in the cracker classes fields up to the last > > private field I need to access so the cracker classes would not brake by > > changing or adding successive fields in the original classes. I assume > > now it is necessary to always list all fields of the original class. > > If would you want to use that optimization, then yes. "Working around" the > type system of the language is however generally asking for trouble, > regardless of what reason you do it for. > I do not necessarily want to use field order optimization but if the FPC RTL is compiled with it I need to compile my cracker classes with optimization too.
Martin _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
