In this case, Clipper Procedures are documented to not return a value, but in
actual fact, you get whatever the last value put on the return stack. Harbour
actually sets that value to NIL.
IOW, the operation is actually 'undefined' in Clipper - or said another way, do
_not_ rely on thsi side effect.
Paul
Date: Wed, 3 Feb 2010 13:50:18 -0800
From: smujohn...@gmail.com
To: harbour@harbour-project.org
Subject: [Harbour] Harbour / Clipper Incompatibility Issue: SETPOS() return val
Hi,
In Clipper, ? SETPOS(10,4) returns 10. In Harbour, it returns NIL
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
