OpenEuphoria

Re: More bugs in exw.exe

• Posted by CChris <christian.cuvier at agriculture?gouv.f?> Jul 17, 2007
• 605 views

Juergen Luethje wrote:
> 
> Rob wrote:
> 
> > CChris wrote:
> > 
> >> 1/ Trying to open C:\VE OPEN\visualeuphoria.exw by double clicking it in
> >> Windows
> >> explorer (or its free replacement) causes interpreter to barf:
> >> Can't open C:\VE.exu
> > 
> > I tested this exact path and filename on my XP system
> > and it worked fine by double-clicking.
> 
> I can confirm this.
> 
> > I'm not sure what happened on your system.
> 
> I also don't know this, of course. However, I can guess that maybe on
> his system in the Windows registry some double quotes are missing at
> a particular place.
> 
> In the message to which Rob replied, CChris had written:
> | This is a bug, since the behaviour is not documented and the above
> | is a valid Windows path.
> 
> But the bug probably is not in the Euphoria interpreter, since the
> _operating system_ controls, what is passed to an application as a
> single parameter, and what is passed as separate parameters.
> 
> Regards,
>    Juergen

Thanks for the tip, I'll check this out tonight.
However, the missing double quotes, if any, come from a faulty file type
association, which points to a likely bug in the installation script. Hence,
while you may be right in that the bug may not be in the interpreter, there would
still be a bug in the Euphoria for DOS/Windows distribution.

While I'm at it:
The install script blindly adds its thing to existing environment variables,
without checking whether that's actually needed. So, you can wind up with an
EUDIR variable containing:
D:\EUPHORIA\BIN;D:\EUPHORIA\BIN;D:\EUPHORIA\BIN;
That's how it looks on my system right now.
While this is not really a bug, as the redundancy hardly matters, this could
become annoying after the 23rd reinstall of Euphoria for any reason. Perhaps an
optimisation is in order there.

CChris