RE: include statement bugs
Igor Kachan wrote:
<SNIP>
> OK, it is great, but why do you think the standard RDS's libraries
> need a new alternative?
It's blatantly obvious that any explanation to you would be in vain.
<SNIP>
> OK, no problem. Add some letter to the name of standard RDS
> library. Me uses the 'r' letter - Russian, say, file___r.e
> instead of standard file.e.
> My file___r.e works in both Russian and English.
> Try please, it is in The Archive.
That means changing the filenames of your precious RDS include files.
> > My libraries use many of the same file names as RDS does,
> > and for good reason.
>
> What is that good reason to make any conflict with the
> standard copyrighted PD programming stuff, 11 years old,
> working without any problem for dozens thousands of users?
> Do you have any respect to those people?
Because backwards compatability is a detriment to the optimal progress.
Because the names are _meaningful_ . Because I CHOOSE to.
Because I'm not going to use obscure names, just because you are too
blind/stubborn to accept the fact that it's perfectly logical to have 2
files with the same name and different content and/or intent.
> > I resent the opinion that I should have to rename all of my
> > meaningfully named files, just to accomodate your ignorance of the
> > problem.
>
> Chris, you have to *name* yours libs *properly* and then
> you'll have no problem.
I DID name my files properly..
I use include statements such as std/util/file.e
and rds/file.e
The fact that RDS is too stupid to realize that it is a very useful
functionality, will be YOUR problem when Euphoria is fumbling with hack
solutions, and you have no choice but to live with it or pick up a new
language. You can rename all your files, I won't. That is perposterous.
Chris Bensler
Code is Alchemy
|
Not Categorized, Please Help
|
|
