1. include vs. include\std
- Posted by kenneth Aug 30, 2009
- 974 views
While running some old programs that included machine.e and dll.e, I was getting nuisance warnings. Finally realizing that I should be including std\machine.e and std\dll.e instead, the problems went away. Why are the old .e files still in the distribution? If they must be included, couldn't they be in their own subdirectory - old\dll.e and old\machine.e for example? Leaving out "std" will be a common mistake until we get used to version 4. Not running at all would be a better default than using the wrong file.
2. Re: include vs. include\std
- Posted by mattlewis (admin) Aug 30, 2009
- 959 views
The v3 standard library is included to be able to run legacy code, of which there's a lot, much of which will run without being changed. The warnings are there to warn you that you're using the old stuff.
Matt
3. Re: include vs. include\std
- Posted by jeremy (admin) Sep 01, 2009
- 829 views
- Last edited Sep 02, 2009
Oh, I'd also like to say that Euphoria fully supports using forward slashes and those are recommended as it will work on Windows, OS X, Linux or any Unix system. Backslashes will not.
include std\sequence.e -- works *only* on Windows include std/sequence.e -- works on any platform Euphoria supports
Jeremy
