Re: Multiple entry tasks

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

Sorry. Force of habit. I generally code comparisons that avoid things like
"X = 0" out of fear that one day, somehow, X may be -1 and that still means
I want to take action based on nothing being there. (The 'Count attribute
returns Universal Integer - so negative numbers are at least within the
set - if not something that would actually get returned.) I've learned
especially to avoid that comparison on floating point numbers and there is
just a sort of paranoia in the back of my mind that wants to account for all
possible - and impossible - conditions. (Forgive us our paranoia, for we
know what we do!)

So if Entry1'Count is > 0, I definitely know I've got entries called - the
negation of that condition is "<=" and that accounts for everything. I
suppose I could have said "not (Entry1'Count > 0)" but that may have been
even more confusing!

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Ted Dennison" <dennison@telepath.com> wrote in message
news:pPCD6.2928$D4.287059@www.newsranger.com...
> In article <9bm76r$mf6$1@s1.read.news.oleane.net>, Jean-Pierre Rosen
says...
> I think the confusing part was that he used "<= 0" rather than "= 0".
'count
> logically shouldn't ever go negative, but I guess he was trying to be safe
> (perhaps there's some degenerate case about that in the LRM. I'd check it
if
> this were production code I was writing). I'd only expected to see a
> two-character boolean of ">= 0", so that's what my brain reported. :-(
>