OpenEuphoria

Re: Packages

• Posted by Pete Lomax <petelomax at blueyond?r?co.uk> Aug 10, 2007
• 510 views

Matt Lewis wrote:
> 
> So if the gui.e guy wanted to be able to see stuff in the memory package
I'm struggling to see why gui.e would want priviledged access to the private
bits of memory.e in a way other components were not allowed. Surely if gui.e
wants to use memory.e it should just stick with the publically defined external
api??

> My concern with this is that everyone has to choose unique package names,
> or libraries with conflicting package names risk leaking into each other.
Hmm. It may be possible to use the one guaranteed unique thing we have to hand:

-- win32lib.ew
package ./win32lib.ew
include file/w32file.e
<eof>
-- w32file.e
package ../win32lib.ew
<eof>

IE the package name is a full expanded path and filename. There may be other
benefits to this, namely not using F:\test\win32lib.ew with
C:\Euphoria\include\w32file.e, which may have version incompatibilities.

Regards,
Pete