Re: Null Capable Fields

I belive something like  " If  FieldName = *Null " will be easier to
understand for the maintenance programmer than " If FieldName =
'SomeNullSymbol'  ", where the 'SomeNullSymbol' is the standard for the
programmer who wrote the aplicaction.

___________________________________________________________________
boothm@earth.goddard.edu wrote:
> 
> Now I am glad I asked the question; it really does amount to a request to
> detect and/or restore virginity.  I can see useful reasons for it, but in
> the example you've shown I came away thinking the real problem is that the
> decision is being removed from the point of original information.  When
> you learn the field is null, and know you need the knowledge later on, fly
> a traditional RPG flag.  There's no reason to lug nulls all around the
> C-specs and compound the lives of those maintenance programmers who come
> after us, is there?
<snip>
-- 
  Raul A. Jager W.
Asuncion - Paraguay

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---