1. wildcard.e
- Posted by CChris <christian.cuvier at agriculture.g??v.fr> Jul 19, 2007
- 594 views
The new routines to case insensitive compare filenames with accented chars work fine, with an unexpected side effect though. Since the couple lines that was using upper() are no longer in scanner.e, wildcard.e is optimised away from compilation, so it seems. To avoid errors first, I plugged a routine_id("upper") somewhere in order to keep going (and got a valid and working exw.exe). But obviously that's a kludge... is it safe to delete _all_ references to wildcard.c/.o/.obj in the doezn batch files, as building the interpreter no longer seems to require this include file? Just cautious. CChris
2. Re: wildcard.e
- Posted by Robert Craig <rds at RapidE?phoria?com> Jul 19, 2007
- 573 views
CChris wrote: > The new routines to case insensitive compare filenames with accented chars > work > fine, with an unexpected side effect though. > Since the couple lines that was using upper() are no longer in scanner.e, > wildcard.e > is optimised away from compilation, so it seems. > To avoid errors first, I plugged a routine_id("upper") somewhere in order to > keep going (and got a valid and working exw.exe). But obviously that's a > kludge... > is it safe to delete _all_ references to wildcard.c/.o/.obj in the doezn batch > files, as building the interpreter no longer seems to require this include > file? > Just cautious. It would be much better to remove all references to wildcard.* from the batch files, than to create an unnecessary reference to upper(). Thanks, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
3. Re: wildcard.e
- Posted by CChris <christian.cuvier at ag?icultur?.gouv.fr> Jul 19, 2007
- 591 views
Robert Craig wrote: > > CChris wrote: > > The new routines to case insensitive compare filenames with accented chars > > work > > fine, with an unexpected side effect though. > > Since the couple lines that was using upper() are no longer in scanner.e, > > wildcard.e > > is optimised away from compilation, so it seems. > > To avoid errors first, I plugged a routine_id("upper") somewhere in order to > > keep going (and got a valid and working exw.exe). But obviously that's a > > kludge... > > is it safe to delete _all_ references to wildcard.c/.o/.obj in the doezn > > batch > > files, as building the interpreter no longer seems to require this include > > file? > > Just cautious. > > It would be much better to remove all references > to wildcard.* from the batch files, than to create > an unnecessary reference to upper(). > > Thanks, > Rob Craig > Rapid Deployment Software > <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a> I'll do so, I was just a little surprised and wished to check the drastic change was the thing to do. I'll commit that tonight (9am here now). CChris