OpenEuphoria

Re: Include system

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Dec 31, 2006
• 1091 views

Derek Parnell wrote:
> I'm not sure if I'm understanding you here. Are you saying that this 
> actually works with Euphoria 3.0 right now?
See
http://www.listfilter.com/cgi-bin/esearch.exu?thread=1&fromMonth=B&fromYear=B&toMonth=1&toYear=C&keywords=%22Include+system+(implementation)%22

Also, it must be over 8 months that I've had this in Positive, though a new
release of that is several weeks away yet.

> If so, I can't get it to work. This is the
> message I get ...
> 
> C:\>exwc C:\projects\eu_proj\win32lib\win32libcurrent\Demo\bitmap.exw
> C:\projects\eu_proj\win32lib\win32libcurrent\Demo\bitmap.exw:1
> can't find win32lib.ew in C:\projects\eu_proj\win32lib\win32libcurrent\Demo

Actually, that's a bit different, since win32lib.ew is not in the \Demo\ folder.
The test you want (I think) is to change
> include win32lib.ew
to
  include ..\include\win32lib.ew

ditto the final line (23) to include ..\include\w32Start.ew

It compiled cleanly for me using cb's exe, whereas it failed on line 501,
include w32Keys.e under 3.0.0


> > > For example's sake, let's
> > > use the symbol "^" to represent the including file's directory.
> > CChris has already beat me to saying that "./" is a much more natural
> 
> I must strongly disagree with you on that point.
> 
> The path "." is already assigned a meaning. It means relative to the 
> current working directory of the shell.
Hmmm.
> And that is why I see the need for either a new special symbol in the 
> include statement to indicate 'relative-to-the-including-file', or the 
> search algorithm must change to do this automatically for all include 
> statements.
As I said above, I put this in 8 months ago, and I think my concept of current
directory has changed, at least while I'm actually compiling a relative include
file. Obviously I don't mean that an open("icons.xpm")
statement within include xpm/xpmlib.ew should (somehow) open xpm/icons.xpm.
You would still have to clutter up the main project directory with files
like that to keep src & exe behaviour equal. (xpmlib is fictional, btw)

Anyway, play with cb's 3.0.1 a while and see what you think.

> 
> Also, I read that some are suggesting the paths beginning with "\" should 
> be interpreted as being relative to the including file.
...
> Thus "\util\series.e" means "series.e" is expected in "C:\util"
I can accept that.

Regards,
Pete