aleks@well.UUCP (Brian J. Witt) (03/27/89)
Yes, a shared library for Eiffel would be very useful. Think of building an operating system where the bulk of the library is the OS itself. Classes like FILE and TASK would be available to all. The application would "simply" be "binded" to these class at load time! To expand the OS, you allow a few more classes to be "accessed" from programs. Anyone have a CM* sysyem gathering dust in the basement? :-) :-) :-) :-) "Creator of AXE OOOS: Amiga uniX Exec - Object Orientated Op System" --- brian witt --- USENET: well!aleks@ucbvax.berkeley.edu
lalonde@nicmad.UUCP (John Lalonde) (03/27/89)
We are considering using Eiffel for new product development. Could someone
at ISE indicate whether or not it would be technically possible to construct
shared libraries (e.g. as in SunOS 4.x) from Eiffel classes. It would very
interesting if this were true because of the flexibility provided by
combining dynamic binding with dynamic link-editing. If one could build
Eiffel classes as shared libraries then field upgrades of software modules
could be handled very cleanly. It would be also be very useful if
collections of Eiffel classes could be organized as a single shared library.
Finally, has anyone experimented with the notion of lightweight processes
and Eiffel objects under SunOS 4.x? Any replies would be greatly appreciated.
Thanks...
--
John LaLonde
Nicolet Instrument Corporation
uucp: {ucbvax,rutgers,harvard}!uwvax!astroatc!nicmad!lalonde
--
John LaLonde
Nicolet Instrument Corporation
uucp: {ucbvax,rutgers,harvard}!uwvax!astroatc!nicmad!lalonde