OpenEuphoria

Re: EE:CS subs listing bug

• Posted by Falkon 1313 <Falkon1313 at AOL.COM> Jun 23, 2000
• 477 views

>From:    "Carl R. White" <cyrek at BIGFOOT.COM>

>On another note: There are 2 other bugs in EE22:CS4 that I'm surprised
>nobody has noticed... Is there anybody apart from me and Skoda using it
>these days? Should I drop the project?

I use an older version daily, and I've got the latest version but I haven't
used it yet.

I found one bug in the older version recently, but it's gone in the new
version.  :)

Okay, first try:

puts( 1, "Blah" )
Save As "Blah.ex"
F5                 (nothing)
Run | Execute (hmm...Execute is dim still, even though the file's
     been saved as an .ex.  That doesn't happen in 2.1CS3)
Close file
Open file "Blah.ex"
F5...crash (no error message, the window just disappeared)

Tried again in full-screen mode and got an error message.
   747 in function is_long_filename() variable BX has not
   been assigned a value

Here's that problem, line 57-61 of is_long_filename() in win95fh.e:
    return
        pos = 1
        or find('.', ext)
        or length(filename) > 8
        or length(ext) > 3
That tests ext, but ext is only set if pos != 0, so if (pos = 0)
ext will be uninitialised.  I'm not sure about the loop in
is_long_pathname() starting at line 79, but it looks to me
like it steps through each part of the path calling
is_long_filename(), in which case is_long_filename()'s pos
will be 0 unless there's a period in every part of the path.

All of that is skipped and it works fine as long as there's a
space somewhere in the path (which must be why it works
fine for some people but not others).  I suppose that could be
fixed by initialising ext to "".

Could copy the for loop starting at EE.EX:line 686 in
read_file() and paste it into editor_save_as() somewhere
so that the executability of a new file gets updated
without having to close and reload it.  Would also need
to call update_main_menu() to get the Execute entry
un-dimmed.  Not sure if anything else would need to be
done.

>How can someone who tests other people's software for a living
>be so bad at testing his own code?!? 

I think you've done an excellent job, especially given the
complexity of  the program.  :)  Testing's always more
difficult the closer you are to the code.

I'll check out the new features later...looks nice.