In our previous episode, Anthony Walter said: > All units my framework uses these types and those two units heavily, and > with an updated fpc trunk compiler they break in a big way. I suspect it > may take a quite a bit of effort on my part to get my codebase and working > with the current trunk version of fpc based on the number and types of > errors I am seeing, some of which are related to generics working > differently (I still have a problem with interfaces in not being > initialized properly at times). I am not sure how to proceed in fixing > these as I feel like this will happen again with another future release of > fpc breaking compatibility with the generics I've written. What should I do?
You are using functionality still in development *in* development version of FPC. That's always risky, and there are no guarantees of timetable there. Moreover, from your message it is unclear what your direct problem is except on the macro scale of "it doesn't work". _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
