RE: include statement bugs
- Posted by Chris Bensler <bensler at nt.net> Oct 19, 2004
- 549 views
Igor Kachan wrote: <SNIP> > Ok, I am not a single reader of yours e-mails, maybe others > want to see your explanations. Most other readers are smart enough to know already, and those who aren't, explanation won't help. <SNIP> > > That means changing the filenames of your precious RDS include files. > > These RDS include files are really precious, any EU user uses them. > > And I do not *change* the standard filenames. > > I just use the standard name as a part of a *new* name of > my *new* include file. The standard filename and the standard > library are untouchable. > > Is it clear? The simple thing, it seems to be, no? > Maybe someone else can explain this trick to Chris? > It is the end user who has to deal with all_of_my_unique_file_names.e *I* can manage *MY OWN* code perfectly fine. <SNIP> > > 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. > > Ok, Ok, Ok, progress-shmogress, ok, but what about "any respect"? > The simple thing too, I think, no? Respect for whom? Respect for the people who are actually trying to produce useful things and are trying to make Euphoria better for everybody? Or do you mean respect for those people who are too ignorant to accept change for the sake of improvement? If you want to run legacy code, use a legacy version of the interpreter. You don't force progress to be hindered because you are too narrow-sighted to realize that THINGS CHANGE. <SNIP> > But what is a reason of your problems? > > Do you want to replace the standard RDS files with your own > unknown for us files? Yes? I didn't say anything about for you. I would be perfectly happy if people like you continue worshipping RDS. > And a good antibug EU resistance doesn't allow you to > make this "buggy revolution"? Yes? You have absolutely nothing to corraborate that accusation. What I would LIKE to do and what I WILL do are two different things. > Yes, I found some of your contributions buggy and > crashed for me. Sorry, Chris ... > Yes, you was out of town for a while... What can I do? I have about 5 contributions left on the archives. I removed all of my code. What is left, is 1 hacked utility, an old set of generated libraries, an old preprocessor designed for eu2.2, DAWG, and a structs library. None of it has been supported by me in over 2 years. And as far as I know DAWG and structs are still stable. Again, your accusation is unfounded. > Well, but EU standard libs never crash on my 5 different > machines. From 386 mainframe to P4 1.8. > > Be careful, please, Chris. > Do not make many noise around yours alternative to RDS libs. > Let us know them first of all. NO, I don't care to involve you in my project. I'm glad to see some of the more astute individuals are already discovering though. <SNIP> > You do not want new names for the new libs, but your reason > seems to be not very good, sorry, sorry, sorry ... My libs are not the problem, they are an EXAMPLE, just like johnny and alfred. I have brought up this issue many years ago, and several times. And RDS's answer has been pretty much the same each time. > PS What is 'perposterous'? - I have > no this rare word in my Muller's dictionary. preposterous, absurd, rediculous, illogical, unreasonable http://dictionary.reference.com/search?r=2&q=preposterous Chris Bensler Code is Alchemy