Re: lynx-dev Concerning the use of abort in the source of lynx

[Vlad Harchev]

On Sun, 4 Jun 2000 address@hidden wrote:

> The latest CHANGES indicate the following:
> 
> 2000-06-02 (2.8.4dev.3)
> * initial support for SOURCE_CACHE_FOR_ABORTED -VH
> 
> Let's lay it on  the line.  Communists programming in the lynx project
> who think it's cute to put the words "abort" and "kill" in the configure
> script and in the above example don't belong in programming and should
> get an honest profession, like bagging groceries.

  To say the truth, I didn't understand the previous sentence in full
since there are grammatical and logical errors (why do you mention 'configure' 
- there is no support for enabling/disabling of this functionality via it).

  First, I'm not a communist (it's obviously brain-damaged "religion" for
alcoholics and old men). Some characterisation about you can easily come to my
mind since you are from Germany.

 As for _ABORTED - in this particluar case the only other reasonable synonim
that came to my mind was _INTERRUPTED which is by far longer. But I don't mind
using 'abort' and 'kill' since these are short words and user can guess what
the commands that contain them could mean without reading documentation. And
as I remember, you were reading this list when we discussed the name of this
setting and when I sent a patch - you suggestions were welcome at that time.

> I'll put it more succinctly:  May God curse the lynx developers who
> allow this practice to continue.

  You are really kind person :)
  I guess why you don't use unixes - you avoid using 'kill' and 'killall'
 commands :)
 
> ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
> 

 Best regards,
  -Vlad


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden