[fpc-devel] Re: JVM: class of XYZ => java.lang.Class
jonas.maebe at elis.ugent.be
Sun Dec 25 22:32:11 CET 2011
On 25 Dec 2011, at 22:26, Sven Barth wrote:
> On 25.12.2011 22:11, Jonas Maebe wrote:
>> The main problem is that the more magic conversions are added to the compiler, the harder things become to maintain (both for the JVM target and for other targets).
> I understand that, but from a user point of view it's rather confusing (Strings are another prominent example here).
Strings /are/ handled by compiler magic in all cases, no?
> It might be a good idea if someone (not necessarily you) writes down these little caveats so that others don't need to hunt down these problems again.
If the header parsing is adapted, most cases should be handled automatically without requiring any compiler changes. Actually, the same could be done with strings (replace all occurrences of JLString in the headers with Unicodestring, and then remove most special code for JLString from the compiler).
More information about the fpc-devel