1. win98 & ver. 4.0
- Posted by bernie Aug 13, 2008
- 1081 views
Is anyone working on getting 4.0 to work on win98 ?
2. Re: win98 & ver. 4.0
- Posted by jimcbrown (admin) Aug 13, 2008
- 1088 views
Is anyone working on getting 4.0 to work on win98 ?
I did. It works.
If it doesn't work, what broke?
Note for those compiling eu 4.0 from source - you need to enable MANAGED_MEM=1 or else the binaries will crash on 98.
Note for those using eubins - jeremy is going to create a separate set of eubins for 98 that are compiled with MANAGED_MEM=1.
3. Re: win98 & ver. 4.0
- Posted by jeremy (admin) Aug 13, 2008
- 1133 views
Note for those using eubins - jeremy is going to create a separate set of eubins for 98 that are compiled with MANAGED_MEM=1.
I did a while ago 
they are in the eubins dir (http://jeremy.cowgar.com/eubins/) as eu40win9x-REVISION_NUMBER.zip
Jeremy
4. Re: win98 & ver. 4.0
- Posted by bernie Aug 13, 2008
- 1110 views
Note for those using eubins - jeremy is going to create a separate set of eubins for 98 that are compiled with MANAGED_MEM=1.
I did a while ago they are in the eubins dir (http://jeremy.cowgar.com/eubins/) as eu40win9x-REVISION_NUMBER.zip
Jeremy
I just downloaded Jermey's
Euphoria Interpreter 4.0 (development) for 32-bit Windows.
SVN Revision 1000
Copyright (c) Rapid Deployment Software 2008
See http://www.RapidEuphoria.com/License.txt
file name to execute?
If I run the demo program window.exw; I get the following :
D:\#eu40\INCLUDE\STD\error.e:48
export has not been declared
export procedure crash(sequence fmt, object data={})
^
Press Enter
Has any one other than a developer been sucessful running
any program on win98 with version 4.0 ??
I am using win98 sp2 on an athlon 900mz with 128meg memory.
5. Re: win98 & ver. 4.0
- Posted by jimcbrown (admin) Aug 13, 2008
- 1112 views
I tried his eubin and it works for me. (The window pops up.)
The error you get suggests you are running eu 3.1 or a really old 4.0, in spite of the "SVN Revision 1000" line.
Why are is your directory named "#eu40" btw?
Note for those using eubins - jeremy is going to create a separate set of eubins for 98 that are compiled with MANAGED_MEM=1.
I did a while ago they are in the eubins dir (http://jeremy.cowgar.com/eubins/) as eu40win9x-REVISION_NUMBER.zip
Jeremy
I just downloaded Jermey's
Euphoria Interpreter 4.0 (development) for 32-bit Windows.
SVN Revision 1000
Copyright (c) Rapid Deployment Software 2008
See http://www.RapidEuphoria.com/License.txt
file name to execute?
If I run the demo program window.exw; I get the following :
D:\#eu40\INCLUDE\STD\error.e:48
export has not been declared
export procedure crash(sequence fmt, object data={})
^
Press Enter
Has any one other than a developer been sucessful running
any program on win98 with version 4.0 ??
I am using win98 sp2 on an athlon 900mz with 128meg memory.
6. Re: win98 & ver. 4.0
- Posted by ne1uno Aug 13, 2008
- 1281 views
Has any one other than a developer been sucessful running any program on win98 with version 4.0 ??
I am using win98 sp2 on an athlon 900mz with 128meg memory.
I am running on an athalon1.13 and win98 sp3b2 from msfn, which might be different enough, but it sounds more like an old executable is involved somehow.
cd eu4/tests exwc t_some.e
the exwc svn 1000 jeremy compiled runs fine, I used it to compile svn1036 yesterday.
are the file association still pointing to a previous exe?
run set from a console and check your path and euinc
set
there are new options to deal with include files from the commandline
exwc -i somepath exwc -C .\euinc.conf text file with euinc paths one per linetry all the square one basic stuff, it should work for you too.
lets see more of the test program that is failing.
7. Re: win98 & ver. 4.0
- Posted by bernie Aug 13, 2008
- 1068 views
Thanks to Everybody that help me.
When I ran a program I was clicking on the program with the mouse;
therefore the program was using the registry information and was using
the wrong version of eu.
If I ran the program from the command line it uses the autoexec.bat
information and ran normal.
I think there should be a note in the install text reminding the user
to be sure to check that their registry is pointing to the same directory
as their autoexec.bat path.
The problem was that because I did not install the eu 4.0 using
an install program because it does not exist yet.
8. Re: win98 & ver. 4.0
- Posted by jeremy (admin) Aug 13, 2008
- 1097 views
Just as a side note, I put out revision 1045 just a short while ago. The previous Win98 executables were revision 1000.
http://jeremy.cowgar.com/eubins/
Jeremy
9. Re: win98 & ver. 4.0
- Posted by bernie Aug 13, 2008
- 1082 views
test.exw
enum ONE, TWO, THREE, FOUR
? ONE
? TWO
? THREE
? FOUR
if getc(0) then
end if
This simple program fails on win98 giving me this error
TEST.EXW:1
enum has not been declared
enum ONE, TWO, THREE, FOUR
10. Re: win98 & ver. 4.0
- Posted by jeremy (admin) Aug 13, 2008
- 1051 views
- Last edited Aug 14, 2008
TEST.EXW:1 enum has not been declared enum ONE, TWO, THREE, FOUR
Bernie, this looks like the same problem as before. enum is a built in keyword and is used in many places in the standard library. We surely would have seen this problem before now if there were a problem. Are you sure the old executable is not running again?
Jeremy
11. Re: win98 & ver. 4.0
- Posted by SDPringle Aug 13, 2008
- 1062 views
- Last edited Aug 14, 2008
Can't we expect the setup program that already comes with 3.1 to be used for 4.0 when it is finally rolled out?
Are we going to see .ex files associated with the DOS32 EUPHORIA or can we expect that to change as the discussion on this Forum?
Shawn Pringle
12. Re: win98 & ver. 4.0
- Posted by jeremy (admin) Aug 13, 2008
- 1087 views
- Last edited Aug 14, 2008
Can't we expect the setup program that already comes with 3.1 to be used for 4.0 when it is finally rolled out?
Are we going to see .ex files associated with the DOS32 EUPHORIA or can we expect that to change as the discussion on this Forum?
Yes, it will use the setup program, however, we certainly do not want alpha, let alone pre-alpha's installing themselves as the default interpreter.
I would like to see .ex associated with exwc.exe, .exd with ex.exe and .exw with exw.exe ... .ex = console program (dos, windows or unix), .exd = dos only program, .exw = windowed program (windows or linux).
Jeremy
13. Re: win98 & ver. 4.0
- Posted by jimcbrown (admin) Aug 13, 2008
- 1054 views
- Last edited Aug 14, 2008
.ex = console program (dos, windows or unix), .exd = dos only program, .exw = windowed program (windows or linux).
Jeremy
I assume then .exu is any unix-only program.
If .exw is any windowed program, then what is an M$-Windows only extension? Most .exw's right now require windows (using win32api or windows .dlls).
14. Re: win98 & ver. 4.0
- Posted by jeremy (admin) Aug 14, 2008
- 1093 views
.ex = console program (dos, windows or unix), .exd = dos only program, .exw = windowed program (windows or linux).
Jeremy
I assume then .exu is any unix-only program.
If .exw is any windowed program, then what is an M$-Windows only extension? Most .exw's right now require windows (using win32api or windows .dlls).
I would do totally away with "only" extensions. Euphoria is the only language I know that does this, yet, hundreds of other languages are cross platform as well. For instance, with a ruby app, you have .rb. Nothing more. That .rb file may be cross platform, may be windows only, may be unix only. Python is .py, C is .c, Icon is .icn, Lisp is .lsp, Scheme is .scm, Java is .java, etc... The only real reason we need anything more than .e and .ex is because on Windows we have multiple interpreters 
We should get in the habit of doing things such as a Windows only program:
-- myapp.exw ifdef !WIN32 then include std/error.e crash("myapp runs only on Windows") end ifdef -- Code for myapp
Jeremy
15. Re: win98 & ver. 4.0
- Posted by m_sabal Aug 14, 2008
- 1051 views
.ex = console program (dos, windows or unix), .exd = dos only program, .exw = windowed program (windows or linux).
Jeremy
I assume then .exu is any unix-only program.
If .exw is any windowed program, then what is an M$-Windows only extension? Most .exw's right now require windows (using win32api or windows .dlls).
I would do totally away with "only" extensions.
This discussion has come up a few times. To reiterate, Euphoria does NOT have platform-specific extensions. I can run exw programs on Linux and exu programs on Windows just fine, thank you very much. The use of the different extensions was by convention, to give the programmer, not the interpreter, a hint that there may be code in the file which is OS-specific. I do agree, though, that as a quality issue, programs that will only run on Windows should have a check and error message for those who try to run it on a different platform.
16. Re: win98 & ver. 4.0
- Posted by euphoric (admin) Aug 14, 2008
- 1075 views
I would do totally away with "only" extensions... We should get in the habit of doing things such as a Windows only program:
-- myapp.exw ifdef !WIN32 then include std/error.e crash("myapp runs only on Windows") end ifdef -- Code for myapp
I like that idea, Jeremy. I would go a bit further maybe: How about something like
requires WIN32 -- or BSD or LINUX or DOS or ANY
That would be the first line of any program and would emulate what you've done above with ifdef. If it's not specified, or ANY is used, then it should work with any interpreter.
17. Re: win98 & ver. 4.0
- Posted by SDPringle Aug 18, 2008
- 1066 views
I think some of you are too eager to change the interpreter itself instead of thinking about how you could use the interpreter's existing framework to accomplish the same results. It is preferable to change or add .e files than to change the backend adding a 'requires' pragma.
Certainly, with ifdef you can now have the interpreter decide to exit or call the Windows version of itself with all of its arguments assuming you are using DOS. (Be careful with spaces)
Shawn
