OpenEuphoria

include paths

• Posted by bensler at mail.com Jan 09, 2002
• 391 views

I spose this is mostly for Rob, but opinions are quite welcome.

I finally got around to checking v2.3, and was very much looking forward 
to the EUINC variable. Being limited to the single include directory was 
quite cumbersome, and a nuisance. EUINC certainly makes
life easier, but I was still hoping for more ;P

Is there a reason you chose not to make the euphoria\include directory 
non-recursive? I try to keep my files organized as much as I can, and 
for me, that means I put all my library files into the inlude directory, 
where they belong, BUT, I would like to be able to have seperate 
directories for major API's.

This is what my EUINC var currently looks like, after one day of setting 
up my EU environment..
EUINC=c:\euphoria\include\w320551;c:\euphoria\include\eX17;c:\euphoria\include\mylibs


As you can see, it's going to get quite long, quite fast.

You can see what I'm getting at..
This should be automatic IMHO. If the include path was recursive even 1 
level, it would be much easier to organize things.

I DO prefer to have the EUINC var, it will be great for distributing 
unbound apps, and adjusting the include paths to relate with the users 
personal setup, and not confined to either having all my libs in my 
program directory or moving them to the users include directory.

On another note..
Rob had mentioned before about updating the trace facility, so one could 
view specific elements, or a  range of elements for a sequence.
Do we gotta wait for v2.4? This and the include path are the only things 
I looked forward to, other than my wish list.

I guess my question is, if and when these things will be implemented.
And where's the 'surprises'?

Chris