On 3 Mar 2003 at 13:14, Frank Heckenbach wrote:
[...]
As you know, in GCC, the difference between static and dynamic libraries is very small. You need some options to create a dynamic lib, and that's all. (When using them, you can force linking static ones with `-static', but otherwise the linker will find dynamic or static ones automatically.)
So if we implement a syntax for `libarary', it should not have any relevance to whether the object code is linked statically or dynamically (or perhaps even as a set of object files).
No, it shouldn't. But it should mean "generate a DLL (Windows) or a .so (Unix), as opposed to a .o". In Windows, there would have to be linking as well, in order to produce the DLL. But I guess GPC can just assume that "library foo" means "GPC -shared foo ...." and let the system deal with the rest as appropriate. It is then up to the programmer (platform dependent) what to do with the generated library.
So I was talking more about the syntactical and semantical aspects of `library' in BP/Delphi, not the implementation details (which includes how to link them).
Ok.
[...]
An alternative could be the use of some symbols instead of new keywords (but I don't have a good idea for this yet), or a combination of keywords, such as `uses external ...' or `uses export ...' or `export uses' etc. (just playing around with words ... ;-).
"propagates"?
"instead of new keywords"!?
No.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/