1. ver 4.0 include problem
- Posted by bernie Sep 01, 2008
- 972 views
Why do include files that are located in the STD directory
include other files in the same directory like the following: ??
file wildcard.e has the following include in it.
include std/text.e as txt -- upper/lower
Because the include file text.e is in the same directory I get this error.
D:\#EU40\INCLUDE\std/wildcard.e:178
upper has not been declared
pattern = txt:upper(pattern)
^
When running ecw -bor eu.ex in the source directory.
This my euinc using set command.
EUINC=D:\#EU40\INCLUDE;D:\#EU40\INCLUDE\STD;C:\wmotor\include;C:\CLIB
Yes I downloaded the latest SVN
2. Re: ver 4.0 include problem
- Posted by DerekParnell (admin) Sep 01, 2008
- 1000 views
- Last edited Sep 02, 2008
Why do include files that are located in the STD directory include other files in the same directory like the following: ??
file wildcard.e has the following include in it.
include std/text.e as txt -- upper/lower
Because those files need routines that are declared in them. In the case above, wildcard.e needs 'upper' and to find it in needs the 'include std/text.e'. It uses "std/" because that is the new standard location for v4 include files. The assumption is that EUINC or equvalent will have "$EUDIR/include" and may not have "$EUDIR/include/std" as well.
Because the include file text.e is in the same directory I get this error.
D:\#EU40\INCLUDE\std/wildcard.e:178
upper has not been declared
pattern = txt:upper(pattern)
^
When running ecw -bor eu.ex in the source directory.
This my euinc using set command.
EUINC=D:\#EU40\INCLUDE;D:\#EU40\INCLUDE\STD;C:\wmotor\include;C:\CLIBYes I downloaded the latest SVN
The error message you are getting is not because the include file is in the same directory. I don't know why you are getting that message, but it ain't for that reason.
What SVN are you actually using and which platform are you testing on?
I'm using SVN 1112 and Windows XP, and I'm not getting this error.
3. Re: ver 4.0 include problem
- Posted by mattlewis (admin) Sep 01, 2008
- 959 views
- Last edited Sep 02, 2008
Why do include files that are located in the STD directory include other files in the same directory like the following: ??
file wildcard.e has the following include in it.
include std/text.e as txt -- upper/lower
Because those files need routines that are declared in them. In the case above, wildcard.e needs 'upper' and to find it in needs the 'include std/text.e'. It uses "std/" because that is the new standard location for v4 include files. The assumption is that EUINC or equvalent will have "$EUDIR/include" and may not have "$EUDIR/include/std" as well.
Although they really shouldn't need them, as the first place that is tried is from the same directory where the including file is located.
Matt
4. Re: ver 4.0 include problem
- Posted by DerekParnell (admin) Sep 01, 2008
- 972 views
- Last edited Sep 02, 2008
It uses "std/" because that is the new standard location for v4 include files.
Although they really shouldn't need them, as the first place that is tried is from the same directory where the including file is located.
Oh!? I wasn't aware of that.
How would I code the situation where I wanted to get a file from the EUINC list rather than the same directory as the file doing the including?
5. Re: ver 4.0 include problem
- Posted by mattlewis (admin) Sep 02, 2008
- 967 views
It uses "std/" because that is the new standard location for v4 include files.
Although they really shouldn't need them, as the first place that is tried is from the same directory where the including file is located.
Oh!? I wasn't aware of that.
How would I code the situation where I wanted to get a file from the EUINC list rather than the same directory as the file doing the including?
The easiest thing would be to have the file you want in a subdirectory off of something in EUINC, similar to how we now have the standard library. Take a look at scanner:path_open() for the actual code that finds the files.
Matt
6. Re: ver 4.0 include problem
- Posted by bernie Sep 02, 2008
- 934 views
It uses "std/" because that is the new standard location for v4 include files.
Although they really shouldn't need them, as the first place that is tried is from the same directory where the including file is located.
Oh!? I wasn't aware of that.
How would I code the situation where I wanted to get a file from the EUINC list rather than the same directory as the file doing the including?
The easiest thing would be to have the file you want in a subdirectory off of something in EUINC, similar to how we now have the standard library. Take a look at scanner:path_open() for the actual code that finds the files.
Matt
Yesterday I went on the internet and downloaded TortoiseSVN. I then installed it on my WIN98 system and checked out the complete trunk from : https://rapideuphoria.svn.sf.net/svnroot/rapideuphoria/trunk I took that SVN and added the include files from ver 3.1.1 into ver 4.0 include directory ( which is the way you said it would work ). I then placed the WIN98 1067 ver of binaries that Jermey had created in thee BIN directory. I then setup my autoexec.bat for euinc and eudir. I also tried just changing the euinc to just point to EU include directory.
7. Re: ver 4.0 include problem
- Posted by euphoric (admin) Sep 02, 2008
- 956 views
I then setup my autoexec.bat for euinc and eudir.
I also tried just changing the euinc to just point to EU include directory.
Bernie, have you set up a euinc.conf file? That's where path data should be now.
8. Re: ver 4.0 include problem
- Posted by bernie Sep 02, 2008
- 962 views
I then setup my autoexec.bat for euinc and eudir.
I also tried just changing the euinc to just point to EU include directory.
Bernie, have you set up a euinc.conf file? That's where path data should be now.
How due you propose that I do that ecw.exe does not except that on
the command line and if I put in the bin it does make any difference.
9. Re: ver 4.0 include problem
- Posted by mattlewis (admin) Sep 02, 2008
- 945 views
I then setup my autoexec.bat for euinc and eudir.
I also tried just changing the euinc to just point to EU include directory.
Bernie, have you set up a euinc.conf file? That's where path data should be now.
How due you propose that I do that ecw.exe does not except that on
the command line and if I put in the bin it does make any difference.
Could you give us an example of the command line that doesn't work? The basic usage should be something like:
> exw -c <path to my config file> <euphoria program> > exw -i <path to a directory to search for includes> <euphoria program>Matt
10. Re: ver 4.0 include problem
- Posted by euphoric (admin) Sep 02, 2008
- 943 views
I then setup my autoexec.bat for euinc and eudir.
I also tried just changing the euinc to just point to EU include directory.
Bernie, have you set up a euinc.conf file? That's where path data should be now.
How due you propose that I do that ecw.exe does not except that on
the command line and if I put in the bin it does make any difference.
Could you give us an example of the command line that doesn't work? The basic usage should be something like:
> exw -c <path to my config file> <euphoria program> > exw -i <path to a directory to search for includes> <euphoria program>Matt
Bernie referenced ecw.exe. Is that the translator? Does it work with euinc.conf?
Also, all paths can go in euinc.conf (at least, that's how I do it).
11. Re: ver 4.0 include problem
- Posted by bernie Sep 02, 2008
- 946 views
I then setup my autoexec.bat for euinc and eudir.
I also tried just changing the euinc to just point to EU include directory.
Bernie, have you set up a euinc.conf file? That's where path data should be now.
How due you propose that I do that ecw.exe does not except that on
the command line and if I put in the bin it does make any difference.
Could you give us an example of the command line that doesn't work? The basic usage should be something like:
> exw -c <path to my config file> <euphoria program> > exw -i <path to a directory to search for includes> <euphoria program>Matt
Matt:
I was talking about ECW.EXE not excepting the -i option.
I downloaded trunk SVN 1067 an exported the files out of
that to my eu dir. then using Jeremy's WIN98 bin I don't
get any include problem now. The only thing I can't do is
build any binaries because I can't use the 1067 binaries
to run with later SVN versions of the includes. I think
that if your binaries get out of sync with the std libraries
your going to run into problems in the future versions.
Is there a SINGLE compiler that can be used to build all
of the binaries at once ??
Bernie
12. Re: ver 4.0 include problem
- Posted by ne1uno Sep 02, 2008
- 1020 views
Yesterday I went on the internet and downloaded TortoiseSVN.
I then installed it on my WIN98 system and checked out the complete trunk from : https://rapideuphoria.svn.sf.net/svnroot/rapideuphoria/trunk
in addition to any other specific problems with paths, some of the current include and error reporting problems can happen because of mismatched executables.
rightclick on your directory in an explorer then instead of update, go into a submenu and update to revision. there is only 1067 win98 binaries compiled so far on eubins, so I'm guessing that is what you are using. update to revision 1067 should work. unless you are using forward references the latest map or the new regex vrs the pcre regex, you probably won't notice much missing.
13. Re: ver 4.0 include problem
- Posted by mattlewis (admin) Sep 02, 2008
- 948 views
I was talking about ECW.EXE not excepting the -i option.
I downloaded trunk SVN 1067 an exported the files out of that to my eu dir. then using Jeremy's WIN98 bin I don't get any include problem now. The only thing I can't do is build any binaries because I can't use the 1067 binaries to run with later SVN versions of the includes. I think that if your binaries get out of sync with the std libraries your going to run into problems in the future versions.
Is there a SINGLE compiler that can be used to build all of the binaries at once ??
No, there is no single compiler, though OpenWatcom can build both DOS and Windows. The translator can cross translate.
Yes, since we have multiple people working, we sometimes get ahead of ourselves, or at least make it so that you have to use a specific sequence of revisions to get a current build. It's a sign of progress. Really. :)
Matt
