OpenEuphoria

2. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

• Posted by euphoric (admin) Nov 05, 2021
• 896 views

C:\CS\exchange\this_exchange.e:1627 in function init() 
fatal exception [MEMORY VIOLATION] at #0068734D 
    iniwall = {1,``} 

Pete! Apparently, I was also one of my hopes... because I got past it!

Here's the diagnosis:

There must be a bug somewhere when trying to assign a value to a sequence that is not yet initialized/defined.

I was trying to do something like this:

    data[NAME] = new_name 

and data[] was not yet defined/initialized.

It would be nice to just get an error message like, "You dun goofed, son," instead of a MEMORY VIOLATION ERROR!

I haven't used Euphoria/Phix in a while for anything serious, and I'm coming back to this particular project. But every time I use Edita, I appreciate the little conveniences and the nice functionality you've built into it. NICE JOB!

There are still some suggestions I have for it, but maybe I'll have to do that myself some day.

4. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

• Posted by euphoric (admin) Nov 06, 2021
• 852 views

Yeah, I have no idea. That's why I leave it to the professionals.

6. Re: [Phix] Fatal Exception [Memory Violation] Crashing App

• Posted by euphoric (admin) Nov 07, 2021
• 797 views

constant NAME = 1 
sequence data 
--?data[NAME] 
 
procedure p() 
sequence data 
--?data[NAME] 
end procedure 
p() 

Yes, they both give nice and clear "variable not defined" errors.

Specifically: variable data has not been assigned a value