I note that Gnoga 2.1a is not backward compatible with 1.6a due to the
introduction of UXStrings. I had hoped that this would only involve overloaded
operations, and that those using String would continue to be available.
In addition to littering my code with conversions to UXString, I would have to
change any sources I have that use the upper half of Character to UTF-8
encoding, as the spec of UXStrings uses non-ASCII characters in UTF-8 encoding,
GNAT's source-based model means that specs are read every time something that
uses the pkg is compiled, so any compilation against Gnoga must use UTF-8
encoding. This seems like excess effort for no gain, so I won't be making the
transition immediately.
However, it appears that 2.1a has resolved the recompilation problem that
plagued earlier versions. What was the culprit and its fix? I would like to see
the fix applied back to earlier versions if possible.
--Jeff Carter"Now go away or I shall taunt you a second time."Monty Python and
the Holy Gral
_______________________________________________
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list
