1. Eu 4.0 bugs
- Posted by Algorythm Nov 30, 2008
- 1046 views
Hi all! I've downloaded the EU 4.0 Alpha. The demo programs works normally, but my own programs don't. I noticed one bug: EUINC (I set it to "D:\EUPHORIA\include\std") is not recepted by interpretor and I had to correct all my includes manually. Well, it isn't too hard but it's boring. But my programs din't work correctly when I corrected includes. Errors resolving the references occured. Howto solve this problems?
In other hand 4.0 works great. Thank you, developers!
P.S. Sorry for my bad English, it is not my native lang.
2. Re: Eu 4.0 bugs
- Posted by mattlewis (admin) Nov 30, 2008
- 1063 views
Hi all! I've downloaded the EU 4.0 Alpha. The demo programs works normally, but my own programs don't. I noticed one bug: EUINC (I set it to "D:\EUPHORIA\include\std") is not recepted by interpretor and I had to correct all my includes manually. Well, it isn't too hard but it's boring.
The proper setup for EUINC would still be to simply euphoria/include. Then, in your code, use "include std/machine.e". This was intentional, in order to prevent difficulties if you want to use another library with a conflicting name. As the standard library has grown, this is more probable.
But my programs din't work correctly when I corrected includes. Errors resolving the references occured. Howto solve this problems?
It's hard to say without more details. Another change to the libraries is that exposed routines are no longer global. They use the slightly more restrictive public scope. A common pattern in euphoria code has been to include all files needed in the main app file, and to have other, helper files rely on those include statements. This won't work with the public scope. You'll need to add include statements for those files where you're getting unresolved references.
Matt
3. Re: Eu 4.0 bugs
- Posted by Algorythm Nov 30, 2008
- 1080 views
Thank Matt for your reply
The proper setup for EUINC would still be to simply euphoria/include. Then, in your code, use "include std/machine.e". This was intentional, in order to prevent difficulties if you want to use another library with a conflicting name. As the standard library has grown, this is more probable.
Ok I said about programs I have already written. I want to set EUINC and don't edit all includes. But it doesn't work (now I see it isn't a bug, it is a feature :) Then I want to use win32lib. My attempt to just edit all includes in win32lib (for exapmle, "include machine.e" -> "include std/machine.e") but it crached.
I have 71 KB ex.err with list of references, resolving them error occured.
Now I see EU 4.0 is uncompatible with old programs and libraries?
4. Re: Eu 4.0 bugs
- Posted by Algorythm Nov 30, 2008
- 1054 views
I try to run win32lib demos and:
D:\tmp\ex00.exw:26016 Errors resolving the following references: D:\EUPHORIA\include\win32lib\w32msgs.e (110): crash_message D:\EUPHORIA\include\win32lib\w32msgs.e (329): upper D:\EUPHORIA\include\win32lib\w32msgs.e (332): upper D:\EUPHORIA\include\win32lib\w32utils.e (634): upper D:\EUPHORIA\include\win32lib\w32utils.e (1915): reverse D:\EUPHORIA\include\win32lib\w32utils.e (2142): set_rand D:\EUPHORIA\include\win32lib\w32utils.e (2147): set_rand D:\EUPHORIA\include\win32lib\w32memory.ew (60): open_dll D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): define_c_func D:\EUPHORIA\include\win32lib\w32memory.ew (62): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (62): C_LONG
etc...
5. Re: Eu 4.0 bugs
- Posted by Don_Cole Nov 30, 2008
- 1065 views
Hi all! I've downloaded the EU 4.0 Alpha. The demo programs works normally, but my own programs don't. I noticed one bug: EUINC (I set it to "D:\EUPHORIA\include\std") is not recepted by interpretor and I had to correct all my includes manually. Well, it isn't too hard but it's boring. But my programs din't work correctly when I corrected includes. Errors resolving the references occured. Howto solve this problems?
In other hand 4.0 works great. Thank you, developers!
P.S. Sorry for my bad English, it is not my native lang.
This is a test. I'm having trouble logging in to this forum.
Sorry Don Cole
6. Re: Eu 4.0 bugs
- Posted by Don_Cole Nov 30, 2008
- 1068 views
Hi all! I've downloaded the EU 4.0 Alpha. The demo programs works normally, but my own programs don't. I noticed one bug: EUINC (I set it to "D:\EUPHORIA\include\std") is not recepted by interpretor and I had to correct all my includes manually. Well, it isn't too hard but it's boring. But my programs din't work correctly when I corrected includes. Errors resolving the references occured. Howto solve this problems?
In other hand 4.0 works great. Thank you, developers!
P.S. Sorry for my bad English, it is not my native lang.
This is a test. I'm having trouble logging in to this forum.
Sorry Don Cole
When I add to an existing message things work ok.
When I try to create a new message, It asks me to login ( I do) and when I hit Post it asks me to login again.
Can't login right.
Don Cole
7. Re: Eu 4.0 bugs
- Posted by DerekParnell (admin) Nov 30, 2008
- 1074 views
I try to run win32lib demos and:
D:\tmp\ex00.exw:26016 Errors resolving the following references:
etc...
I'm not sure what the install instructions were for the alpha-v4 but they should have included the idea that EUINC be set to ".../include" (as would be the case in v3) and that the v3 include files be copied to that location, and that the v4 includes be placed in the "std" directory which is a sub-directory of the EUINC location.
So you end up with ...
.../include/ <v3 includes> .../include/std/ <v4 includes>When you do this, existing code will use the v3 includes until they are explictly changed to use v4 stuff.
8. Re: Eu 4.0 bugs
- Posted by Algorythm Dec 01, 2008
- 1046 views
Well
I tried to write a program with such functions as crash and other, resolving which error occured. And my program works normally. So it is problem with win32lib. It's really uncompatible with Eu 4.0.
But I found another bug 
. When I'm running sanity.ex with ex.exe it does not puts correctly, (pseudographic instead letters) but under exw.exe it works correctly.
A, is it neccessary to use full-screen mode in ex.exe?
Thank you.
9. Re: Eu 4.0 bugs
- Posted by DerekParnell (admin) Dec 01, 2008
- 1055 views
Well
I tried to write a program with such functions as crash and other, resolving which error occured. And my program works normally. So it is problem with win32lib. It's really uncompatible with Eu 4.0.
What is incompatible with Eu 4.0? Win32lib or your program?
I have just run most of the demo programs that come with win32lib, using eu 4.0, and they are all working. What is the specific problem (and error message) you are getting? Can you show us the smallest program that demostrates the problem?
But I found another bug . When I'm running sanity.ex with ex.exe it does not puts correctly, (pseudographic instead letters) but under exw.exe it works correctly.
I just ran sanity.ex and did not see this problem. I did notice that when using ex.exe (the DOS Euphoria) that it was skipping some tests, but I fixed that just now and it still runs fine.
A, is it neccessary to use full-screen mode in ex.exe?
For the moment, yes it is.
10. Re: Eu 4.0 bugs
- Posted by Algorythm Dec 01, 2008
- 1048 views
Well
I tried to write a program with such functions as crash and other, resolving which error occured. And my program works normally. So it is problem with win32lib. It's really uncompatible with Eu 4.0.
What is incompatible with Eu 4.0? Win32lib or your program?
I have just run most of the demo programs that come with win32lib, using eu 4.0, and they are all working. What is the specific problem (and error message) you are getting? Can you show us the smallest program that demostrates the problem?
But I found another bug . When I'm running sanity.ex with ex.exe it does not puts correctly, (pseudographic instead letters) but under exw.exe it works correctly.
I just ran sanity.ex and did not see this problem. I did notice that when using ex.exe (the DOS Euphoria) that it was skipping some tests, but I fixed that just now and it still runs fine.
A, is it neccessary to use full-screen mode in ex.exe?
For the moment, yes it is.
Derek, all win32lib demo programs don't works on my computer (WinXP if it is important). And my program too.
I'm gettin' this ex.err when i'm trying to run it (it is little part of this file because the original file is too big (71K)):
ex00.exw:2908 Errors resolving the following references: D:\EUPHORIA\include\win32lib\w32msgs.e (110): crash_message D:\EUPHORIA\include\win32lib\w32msgs.e (329): upper D:\EUPHORIA\include\win32lib\w32msgs.e (332): upper D:\EUPHORIA\include\win32lib\w32utils.e (634): upper D:\EUPHORIA\include\win32lib\w32utils.e (1915): reverse D:\EUPHORIA\include\win32lib\w32utils.e (2142): set_rand D:\EUPHORIA\include\win32lib\w32utils.e (2147): set_rand D:\EUPHORIA\include\win32lib\w32memory.ew (60): open_dll D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (61): define_c_func D:\EUPHORIA\include\win32lib\w32memory.ew (62): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (62): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (62): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (62): define_c_func D:\EUPHORIA\include\win32lib\w32memory.ew (64): C_POINTER D:\EUPHORIA\include\win32lib\w32memory.ew (64): C_INT D:\EUPHORIA\include\win32lib\w32memory.ew (64): define_c_func D:\EUPHORIA\include\win32lib\w32memory.ew (65): C_POINTER D:\EUPHORIA\include\win32lib\w32memory.ew (65): C_INT D:\EUPHORIA\include\win32lib\w32memory.ew (65): define_c_func D:\EUPHORIA\include\win32lib\w32memory.ew (162): crash_message D:\EUPHORIA\include\win32lib\w32memory.ew (174): free D:\EUPHORIA\include\win32lib\w32memory.ew (194): allocate D:\EUPHORIA\include\win32lib\w32memory.ew (1265): crash_message D:\EUPHORIA\include\win32lib\w32memory.ew (1308): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (1308): C_LONG D:\EUPHORIA\include\win32lib\w32memory.ew (1308): C_POINTER D:\EUPHORIA\include\win32lib\w32memory.ew (1308): define_c_func
Ho, I wrote own test program
include win32lib\win32lib.ew constant myWin = create (Window, "eu40 test", 0, 0, 0, 200, 100, 0) WinMain(myWin,Normal)
and this doesn't work too. It gives me the same ex.err. It's the smallest program.
About sanity.ex, I can to upload a screen-shot to show you what happened.
TNX!
