Re: Comparing Sequences
This discussion is heading in an interesting direction. I don't really
have much to comment on this issue simply because I doubt it would affect
much, if any of my code (and I would suspect that the previous lack of
comments on the subject would be due to this very reason). I'm one of
those people who do things 'according to spec'. But looking at the
arguments, I'd have to lean more towards David's side of the issue. But
what do I know...
The real purpose of this reply is to get clarification on the following:
On Fri, 6 Oct 2000 20:21:48 CDT, Lewis Townsend wrote:
>Don't change how the operators work, change how the conditional
>statements work. If conditional statements could handle
>sequences as boolean values, instead of breaking code it would
>allow new code to work. For example:
>
>if "Hello" = "Help!" then
>
>which becomes
>
>if {1,1,1,0,0} then
>
>which becomes
>
>if (1 or 1 or 1 or 0 or 0) then -- notice "or" instead of "and"
>
>which becomes
>
>if 0 then
While there is a point made to emphasize 'or' instead of 'and', somehow the
result of (1 or 1 or 1 or 0 or 0) is 0. Doesn't (1 OR whatever) get 'short
circuited' to 1? Did I miss something in the argument or is Lewis
suggesting we redefine logic?
-- Brian
|
Not Categorized, Please Help
|
|