Re: include statement bugs
- Posted by Patrick Barnes <mrtrick at gmail.com> Oct 19, 2004
- 708 views
On Tue, 19 Oct 2004 11:04:42 +0300, Igor Kachan <kinz at peterlink.ru> wrote: <SNIP> > Poor johnny & alfred! They'll never use Euphoria anymore! > Poor johnny & alfred! They'll never use Euphoria anymore! > Poor johnny & alfred! They'll never use Euphoria anymore! > > > > Hey, Dear EU users, never shroud your code please! > Just to be immortal ... Me almost never shrouds ... Igor, it's obvious that you feel strongly about this issue... why? Euphoria as coded assumes that files with the same name are the same file. As Rob himself has stated, this is a HACK. A quick-and-dirty, i-can't-be-bothered-implementing-it-properly HACK! It never should have been like this in the first place. The only reason it is like this is due to laziness. (Or, giving Rob the benefit of the doubt, other developmental pressures) You're quite adept at attacking those who submit reasons why it should be fixed, but you haven't given any reasons for keeping the HACK as it is. Please, tell us. Why should it stay as it is? I believe that Euphoria should NOT assume that 2 files in different locations are the same file. This is because: 1. It produces unexpected, undocumented behaviour. 2. It is illogical. There is no supporting argument for keeping it as-is 3. It makes using third-party libraries more difficult. -- MrTrick