Re: Real world example of the includes-with-the-same-name "bug"
Jason Gade wrote:
> This started working in one of the 2.5 alpha or beta interpreters, but he
> squashed
> it as soon as it was pointed out.
It worked with Euphoria v2.4 and older when the foward slashes were used. Robert
has changed it in 2.5 after a quick decision. I think he knew about it for quite
awile but probably was reluctant to change it in fear of angering Chris Bensler
and others. :P
I think he changed it because the way it worked was by a glitch and wasn't
designed to do that and only worked when using foward slashes and no quotes (no
absolute paths). It was alot easier for Rob to fix it the normal than to go with
the proper solution.
> He doesn't want the interpreter to work this way.
> And it wasn't designed for "internal simplicity".
He didn't want to add code to resolve slashes, dots, etc. or build full paths
from relative and main path directories.
I think he would prefer the proper way, but just doesnt see it as a big enough
issue to warrent the extra hassle fixing it. I'll make it very simple for him.
All he needs to do is backup his scanner.e and replace it with mine. My scanner.e
is based on the multi-tasking PD-source update. So there shouldn't be any issues
unless he's modified his copy since then. If he did, it would be simple for him
to copy and paste his modified code into the my scanner.e or visa versa. He can
remove my comment tags if he likes.
BTW... I was able to get the largest Win32Lib (IDE too), wxEuphoria, FluidAE,
etc. programs to load correctly, so that means everything is pretty dang stable,
though I ran into a several bugs in the beginning but fixed them quickly.
I want to refine the slash scanner a little more and maybe optimize the code a
little before release it (there is no noticable difference in loading time).
Regards,
Vincent
|
Not Categorized, Please Help
|
|
