From: SourceForge.net <no...@so...> - 2009-07-14 13:59:20
|
Bugs item #2821033, was opened at 2009-07-13 17:57 Message generated for change (Settings changed) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2821033&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Doug Lorch (douglorch) >Assigned to: Mark Miesfeld (miesfeld) Summary: Incompatible event semaphore function results Initial Comment: 1. In 4.0.0, e=SysOpenEventSem(xx) returns "00000000" whereas in previous releases it returned "0" when the event does not exist, which means "e==0" now fails. 2. In 4.0.0, e=SysCreateEventSem(xx) returns a hex string (e.g., "000001B8") whereas in previous releases it returned a decimal number, which means "datatype(e,'w')" now fails. REXX-ooRexx_4.0.0(MT) 6.03 30 Jun 2009. Up to date Vista. ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2009-07-13 20:52 Message: The documentation for SysOpenEventSem() and SysCreateEventSem() say that the return is a "handle". Handles are opaque types and as such should only be used as arguments in functions calls that specify they take a "handle" as an argument. In particular this means that using it in a call to datatype() is incorrect. However, there does need to be a return that signals failure. This is complicated here by the fact that the earlier implementation of functions that return handles sometimes used a return of 0 and sometimes a return of "" to signal failure. I'll have to talk this over with Rick to see how he wants to handle this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2821033&group_id=119701 |