RE: Another ELKS idea for shared libraries

[Michael G Hughes]

>Currently, the biggest
>problem with shared libraries on 8086 and bcc is that the compiler can't
>produce position-independent code (ala -fPIC) so that even the code segment
>requires data relocations, and thus can't be shared.  So each process has 
>it's
>own copy.

What about just using DS/CS as they were designed (as I believe is done 
for task switching), can bcc handle that?  Or create something like an 
indirect jump and glue code in the library.