1. BIG PROBLEMS (Rob, again)
Hello again,
Why doesnt this work:
--Calls.ew----------------------------
--Some function calls.--
--At the end of the file:
global procedure SetXyz(atom x)
end procedure
--------------------------------------
Doesnt cause a syntax error, but another function fails
with a strange error saying one of the c function calls
"takes 0 arguments not 1", when it clearly takes 1 pointer.
Ok, got that so far? Now...
Change:
global procedure SetXyz(atom x)
end procedure
To:
global procedure SetXyz()
end procedure
(in other words, remove the private variable declaration)
And all of a sudden the c function call works fine! Just
as good as it had been working all along untill i added
the SetXyz function with a private variable.
Any ideas?
This looks highly unstable.
Take care,
Al
2. Re: BIG PROBLEMS (Rob, again)
Al Getz wrote:
> Why doesnt this work:
Please post here, or send me, your code
(or a stripped-down version that still fails).
Your verbal description is not enough for me
to start debugging anything.
I've received no other bug reports for 2.4 beta
(or any other release) that resemble what you describe.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: BIG PROBLEMS (Rob, again)
>Doesnt cause a syntax error, but another function fails
>with a strange error saying one of the c function calls
>"takes 0 arguments not 1", when it clearly takes 1 pointer.
Sounds a lot like you had defined a c proc/func to take no arguments and
then try to pass an argument to it with c_proc/func().
