Hi Randy,
Now that you say I had a though session
with a DO CASE construct comparing integers
to my custom NumAnd16() function returning
an int with _retni(). It sometimes worked,
sometimes not. The "solution" was to use
the reverse order that you say.
I still can't explain that odd behaviour.
Brgds,
Viktor
On 2008.06.24., at 14:29, Randy Portnoff wrote:
I think it's a bug in Clipper because...
CASE 1 == n
...will work. In fact, when I used to develop using Clipper, I would
always make sure the possible NIL value was on the right side of the
expression.
At 08:01 AM 6/24/2008, you wrote:
Hi all,
Here's an interesting one:
--- code
PROC MAIN()
LOCAL n := NIL
DO CASE
CASE n == 1
? n, "eq 1"
OTHERWISE
? n, "neq 1"
ENDCASE
RETURN
---
--- Clipper 5.2 and 5.3 results
Error BASE/1070 Argument error: ==
Called from MAIN(15)
--- Harbour r8824 result
NIL neq 1
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
