You are not logged in.
Pages: 1
See the description of my pull request on https://github.com/synopse/mORMot/pull/133 .
FPC revision 39684 (during FPC 3.3.1 development) changed the way you have to access this information. In FPC revision < 39684, you must use "@VMP^.Name". In FPC revision >= 39684 you must use "VMP^.NamePtr".
The FPC revision 39684 happened during the FPC 3.3.1 development.
The patch from https://github.com/synopse/mORMot/pull/133 assumes that:
- You either use FPC 3.1.1.
- Or you use FPC 3.3.1 with revision >= 39684.
The original poster uses FPC 3.3.1, revision 39711. This should be supported. The VER3_1 should not be defined, and the correct approach ("VMP^.NamePtr") should be used.
(Note: I removed my earlier answer, I made a mistake there This answer is correct.)
I'm really happy that you will continue your work. Hopefully, having the creative control over NewPascal will allow you to develop new ideas easier, with a peace of mind. I'm waiting with anticipation for new features that you will implement
I have just updated https://castle-engine.io/supported_compilers.php to explicitly say that Castle Game Engine is working with NewPascal.
Much respect,
Michalis
Pages: 1