2017-01-31 14:56 GMT+01:00 Sven Barth <pascaldra...@googlemail.com>:
> I "ignored" it, cause up to now it was merely a performance improvement.
> If you had added your info from 31305 to 31249 instead of creating a new
> report then I might have reacted faster.
>
Very sad info. 31305 costed me additional time. 31305 is separate problem
so has separate ticket. I didn't knew about 31305 until today.
> Anyway, I'll try to get it applied tonight.
>
> PS: If you adjust mORMot then I highly suggest you not to use custom
> records/objects, but the typinfo ones as much as possible as they deal with
> alignment issues correctly (especially the new types of the interface
> RTTI). Or at least use the typinfo types to retrieve pointers to the
> correct parts of the RTTI and store those instead of using inc()s to
> navigate the RTTI.
>
Not that simple, almost impossible to use only TypInfo. mORMot has support
for very large range of compilers: FPC >= 2.6.4 and Delphi >= 5... Custom
records/objects are often the only way to keep sensible code base... mORMot
has own aligntoptr implementation (which is different for each compiler and
platform if needed). aligntoptr is used together with inc()s. TypInfo is
generally incompatible in many ways between Delphi and FPC so we have a lot
of $IFDEFs for low level RTL / RTTI and own structures.
Thanks to mORMot and NewPascal initiative ("fork" is wrong word - NewPascal
exist like more stable predictable trunk with few additional
features/previews) we can keep real single code base between Delphi and FPC.
--
Best regards,
Maciej Izak
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
