10.01.2011 17:40, Jonas Maebe пишет:
On 10 Jan 2011, at 14:46, Alex Shishkin wrote:
By the way despite the fact that static linking to external libraries
will be impossible, but dynamic linking could be implemented. Anyway
I understand that platform independence of code imposes certain
restrictions and that restrictions impact on application design. F.e.
interface to external platform dependent systems should be isolated
in separate package (as I wrote about LCL and its widget sets). But I
think it makes design better.
What you are proposing is something similar to Google Native Client
(http://code.google.com/p/nativeclient/), except that they also added
code verification because it's intended for running native
applications downloaded from websites.
Interesting link. Thanks.
That is not directly related to packages, but rather to a completely
new run time environment with its own ABI, object format etc.
object format is the main question as for now.
The result of having such an environment is indeed that you can have
compiled binary code that is portable across different operating
systems, but that's outside the scope of adding packages support to FPC.
OK
You first have to define such a platform (or you can take the Google
Native Code platform), then add RTL and compiler support to FPC for
that platform, and subsequently any program or package compiled for
that platform by FPC will run on it. Reinventing such a platform and
embedding it in FPC and its run time library falls outside the scope
of the FPC project.
Yes, my implementation of packages planed to be just a platform from the
compiler side. So then "native" support of packages will be added in FPC.
Jonas
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
