The old version (MP2.02) was a fully integrated system - everything written in Visual C.
The beta version (MP3.0) uses a DLL for the compiler, which will be slower. The DLL is compiled with GNU GCC (free and open source!!), which will usually also be slower than a Microsoft compiled DLL.
I do not think compile time is a 'major problem'. It is inconvenient, but not really a problem.
We hope to create a Delphi version of the compiler, which will integrate into the IDE and probably increase the speed.
wes … (Admin)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oposum: Sorry for the delay. Are you sure it is the compiling time of the classes what takes 4 times more time? Here in my tests the only thing that could take significantly more time is the resource files additions to the JAR file (which occurs inside the building process but after the classes compilation stage), and is only newsworthy in projects with many many resource files, is this your case?. In any case I will add an item to my TODO list to try to improve the way I'm using the TurboPower's Abbrevia library, if there is another way. Thanks for the report!
Wes: Thanks for replying.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Major problem with compiling time. It takes 4 times longer than old comercal version. It's possible to fix ?
Thanks for your comment.
The old version (MP2.02) was a fully integrated system - everything written in Visual C.
The beta version (MP3.0) uses a DLL for the compiler, which will be slower. The DLL is compiled with GNU GCC (free and open source!!), which will usually also be slower than a Microsoft compiled DLL.
I do not think compile time is a 'major problem'. It is inconvenient, but not really a problem.
We hope to create a Delphi version of the compiler, which will integrate into the IDE and probably increase the speed.
wes … (Admin)
Oposum: Sorry for the delay. Are you sure it is the compiling time of the classes what takes 4 times more time? Here in my tests the only thing that could take significantly more time is the resource files additions to the JAR file (which occurs inside the building process but after the classes compilation stage), and is only newsworthy in projects with many many resource files, is this your case?. In any case I will add an item to my TODO list to try to improve the way I'm using the TurboPower's Abbrevia library, if there is another way. Thanks for the report!
Wes: Thanks for replying.