using pipe in conditions

[Jay R. Ashworth]

On Wed, Jan 31, 2007 at 09:27:41AM -0500, Kenneth Brody wrote:
> Quoting Walter Vaughan (Wed, 31 Jan 2007 07:30:52 -0500):
> [...]
> > Scott, I guess it's unfortunate that in this example most filePro
> > developers use the pipe character as a field separator. It has no
> > effect other than acting as a separating entity. Anything *houldn't*
> > be in your data, is visible, and is below chr("128") are candidates
> > for replacing the pipe in the above example.
> [...]
> 
> Is there a reason you say 'below chr("128")' in your statement?
> Wouldn't the following work just as well?
> 
>     zz = chr("255")
> 
>     if:  zz&"a"&zz&"b"&zz&"c"&zz co zz{aa{zz
> 
> Aside from the "less friendly looking" line, the above should work
> just as well.

Certainly.

But "the programmer is able to type it into the code easily" is a
non-trivial criterion.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274