Difference between revisions of "User:AlexVinS/Packages"
From Free Pascal wiki
Jump to navigationJump to search (cat) |
|||
| Line 13: | Line 13: | ||
* How exceptions objects should be transfered between executable and packages? | * How exceptions objects should be transfered between executable and packages? | ||
* The package binary format (ELF, FatELF based?) | * The package binary format (ELF, FatELF based?) | ||
| − | |||
* Can RTTI help to access objects from exe by package and vice versa? Use only interfaces or macpas external objects? | * Can RTTI help to access objects from exe by package and vice versa? Use only interfaces or macpas external objects? | ||
| Line 28: | Line 27: | ||
* Classes can be imported from dynamic library. It means that macpas extension should be enabled for "normal" classes and objects. | * Classes can be imported from dynamic library. It means that macpas extension should be enabled for "normal" classes and objects. | ||
* library should be shipped with set of include files, wich defines interface of exported symbols as .h files in c/c++ do. | * library should be shipped with set of include files, wich defines interface of exported symbols as .h files in c/c++ do. | ||
| + | |||
| + | [[Category:Proposals|Packages]] | ||
Revision as of 18:09, 13 January 2011
Delphi style
Platform dependent
Semi-crossplatform
- New system crossplatform.
- os independent, but depends on CPU. Example targets i386-crossplatform ia64-crossplatform
- OOP interface (ojpas interfaces based) between host executable and package RTL, extensible to communicate with concrete packages.
- Host executable memory manager shared with package libs.
- Package binary file format.
- Require to be fully portable (not depends of target system and cpu)
Questions
- How exceptions objects should be transfered between executable and packages?
- The package binary format (ELF, FatELF based?)
- Can RTTI help to access objects from exe by package and vice versa? Use only interfaces or macpas external objects?
Known issues
- win32
- manually loaded binary must (of this restriction could be circumvented?) be copied to another location to mark memory executable.
Full crossplatform
- some kind of byte code, like Java, CLR, LLVM
C++ style
- Executable and its plugins shares same rtl in statically linked library (memory manager shared so classes and longstrings can be passed between modules).
- Classes can be imported from dynamic library. It means that macpas extension should be enabled for "normal" classes and objects.
- library should be shipped with set of include files, wich defines interface of exported symbols as .h files in c/c++ do.
