Difference between revisions of "User:AlexVinS/Packages"

Revision as of 18:24, 11 January 2011

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)

How exceptions objects should be transfered between executable and packages?
The package binary format (ELF, FatELF based?)
The package main source file format (lpk?)
Can RTTI help to access objects from exe by package and vice versa? Use only interfaces or macpas external objects?

manually loaded binary must (of this restriction could be circumvented?) be copied to another location to mark memory executable.

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.

@@ Line 25: / Line 25: @@
 == C++ style ==
-* Executable and its plugins shares same rtl in statically linked library
+* 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.
+* 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.