Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: The joy of FORTRAN
Date: 1 Mar 2025 21:05:10 GMT
Lines: 13
Message-ID: <m2hb45Fcd15U2@mid.individual.net>
References: <5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com>
	<cxicnVzg_cn_eGX7nZ2dnZfqnPadnZ2d@earthlink.com>
	<vdapbn$1kp35$5@dont-email.me> <lltpunF4fseU2@mid.individual.net>
	<1smdnSjX3YoxgWf7nZ2dnZfqn_idnZ2d@earthlink.com>
	<llv30aFa6uvU3@mid.individual.net> <vde4b8$268qv$22@dont-email.me>
	<1396870532.749421730.052473.peter_flass-yahoo.com@news.eternal-september.org>
	<wrapper-20241001111737@ram.dialup.fu-berlin.de>
	<vpl5uk$hhk$3@reader1.panix.com>
	<c4acndn4jJXKwCP6nZ2dnZfqnPSdnZ2d@giganews.com>
	<1214951717.762291306.657281.peter_flass-yahoo.com@news.eternal-september.org>
	<gIUvP.1415795$21T3.138928@fx18.iad> <vpp6b0$31cet$2@dont-email.me>
	<5DWdnXyIYo7er136nZ2dnZfqnPednZ2d@giganews.com>
	<vppkbv$33b82$6@dont-email.me> <vpqm2d$39d65$1@dont-email.me>
	<-ducnbYn4JrmyFz6nZ2dnZfqn_idnZ2d@giganews.com>
	<m2d8haFnv00U2@mid.individual.net>
	<4rOcnbWnvNi3L1z6nZ2dnZfqn_GdnZ2d@giganews.com>
	<20250228094215.00001e7e@gmail.com> <vptb92$3r2n0$16@dont-email.me>
	<k6KwP.62412$OrR5.3167@fx18.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net NmYvlmqZBPkMYQCPs2c4cgJvZ0+Upj1LxuPYDGbvWv3kc2o1dK
Cancel-Lock: sha1:qMOoL8MigwWglY+cSTfYZ29TYOk= sha256:6yzDp7Qo0oE/2NEmwHb9EVbOP+M5LC4+i+Xs70D4Olw=
User-Agent: Pan/0.160 (Toresk; )
Bytes: 2116

On Sat, 01 Mar 2025 20:29:04 GMT, Charlie Gibbs wrote:


> In any piece of commercial software, anyone who sees such a limitation
> as a bug would be rebuffed with the standard response (all together
> now):
> "That's not a bug, it's a feature!"

I found a long standing bug that allowed one resource, police, emt, or 
fire apparatus, to be attached to two different incidents at the same 
time. A client who had found the bug and exploited it as a feature was 
pissed.