Hi,
Przemysław Czerpak wrote:
Perhaps we must leave this hack, or... extend default error handler
Here is the problem with custom user code using own error handlers.
I'm afraid it's hard to change it because it may introduce very serious
bugs to valid Clipper code.
I also do not like it but I'm afraid we have to leave it.
Viktor wrote:
IOW to me the real solution looks rather like
to use subCode only to return ADS specific error
codes. "subCode" is a private matter of any given
RDD (or library), so we don't need to be compatible
with anything here.
So we have two choices:
1) osCode=AdsError and hack for sharing violation (osCode=32,
subCode=AdsError);
2) subCode=AdsError and not Clipper compatible subcodes for not ADS
errors like EDBF_DATAWIDTH, etc. One of ways to solve ambiguity in this
case is error code ranges. ADS uses error codes > 1000. Not ADS errors
can be used from interval 1...999. We can even use "semi-compatible" DBF
error in some cases, using EDBF_* - 1000, because all EDBF_* are below
2000.
What solution do you prefer?
Regards,
Mindaugas
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
