What has happened to comity
- Posted by Everett Williams <rett at GVTC.COM> Feb 13, 2001
- 450 views
Chris, Martin, Al, Graeme, Raude, and others What has happened to comity on this list. MTS starts to clean up his act and then so many of you seem to see the necessity to replace his former attitude with your own. We may disagree, but why the necessity for ridicule and profanity. The latest came from Al in private post. Here is what I posted to him. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >Al, >Your example, while well stated has in it the seed of it's own >destruction. >>For example: >> "file1.ew" contains: >> external_global_prefix="ClassA" >> atom x,y >> x=3 y=4 >> "file2.exw" contains: >> include file1.ew >> atom a,b >> a=ClassA.x >> b=ClassA.y >Note that your "external_global_prefix" is within the included file >requiring whomever wishes to change it to edit the include file. For >future purposes, I hope there will be a day when I cannot look inside >some include files. On principal, I should not need to look inside or >edit someone else's include file. The "include xyz.ew as abc" eliminates >that need and solves all the potential problems that your's creates. It >is only an extension to the current include that does not affect current >usage, while the "external_global_prefix" creates a new variable type. >The "external_global_prefix" also demands that I create two completely >separate files if I wish to include the same file twice. With the >"include ...as..." form, I can include the same file as many times as >>necessary without the confusion of tracking multiple copies of the same >>include. >An even more common problem would occur with things like Win32lib. >I really only want one copy of that include file in my world, but I >definitely want to have the ability to use different prefixes as I >include it in multiple programs. With your "global_external_prefix", that >>would not be possible. I would have to create one copy of the lib for each >>prefix that I wished to use. Everett L.(Rett) Williams @@@@@@@@@@@@@@@@@@@@@@@@@@ and this was his reply: @@@@@@@@@@@@@@@@@@@@@@@@@@ >Then dont use it asshole. @@@@@@@@@@@@@@@@@@@@@@@@@@@ Unsigned, and then when I replied, found his "xaxo at aol.com" blocked. Here was and is my reply, since I cannot reach him directly. @@@@@@@@@@@@@@@@@@@@@@@@@@ Al, Nothing that I said should have caused you to reply in that fashion. I provided you with a carefully reasoned critique of your proposal without cursing or denigrating you. Why such a response. If I am wrong, tell me where I have erred. I intended no personal insult, and after rereading my post to you, I can find no trace of any insult. I am very interested in the possible namespace change and I thought that I provided you with clearly reasoned objections to the form that you proposed. I also provided some arguments for an alternative form that is not original to me, but that I support. In general, I have enjoyed your posts and usually agree with you. What am I missing here. Everett L.(Rett) Williams rett at gvtc.com @@@@@@@@@@@@@@@@@@@@@@@@@@ What can be gained by such savagery. Shall all that is left of Euphoria be a group of coders that accept whatever is tossed their way and code, code, code. Effectively, you are telling me that I should leave all the thinking to Rob. Several have attacked others that have proposed changes to the language, however politely. Neither Ray Smith nor George Henry has done anything particularly provocative, but they have received some criticism unrelated to their suggestions, but only to the fact that they have made suggestions. And both of them have met your criteria that they MUST contribute code. This logic seems to be taking full root on the new list and I cannot believe that it will benefit the language in the short or long run. Everett L.(Rett) Williams rett at gvtc.com