Menu
▾
▴
Re: [Oorexx-devel] 2821033 Incompatible event semaphore function results
|
From: Rick M. <obj...@gm...> - 2009-07-14 14:00:46
|
nope, be my guest. I won't be able to look at this until later this evening, at the earliest. I just looked at the unix versions, and they have been converted to the new format, returing a uintptr_t value. Those will need to have the return type changed to RexxObjectPtr and return either a null string or context->Uintptr(result). Rick On Tue, Jul 14, 2009 at 9:56 AM, Mark Miesfeld<mie...@gm...> wrote: > Okay, > > I'll assign this to myself and do the work, if you haven't already started? > > -- > Mark Miesfeld > > On Tue, Jul 14, 2009 at 6:52 AM, Rick McGuire<obj...@gm...> wrote: >> I think this just needs to be the latter, which is fairly trivial to >> implement. The Windows versions of these >> functions haven't even been converted to the new APIs, but there was >> some cleanup done for 64-bit >> considerations that didn't take into account the failure scenarios. >> The hardest part of this >> will be checking what the failure returns were in 3.2.0 so we change >> the right stuff. >> >> Rick >> >> On Tue, Jul 14, 2009 at 9:44 AM, Mark Miesfeld<mie...@gm...> wrote: >>> Rick, >>> >>> What are your thoughts on how to deal with the Windows RexxUtil >>> functions that return handles, when the function fails? >>> >>> The docs say, returns a handle or 0 on failure for some of the >>> functions. Unfortunately, some of them say returns a handle or the >>> empty string on failure. >>> >>> In ooDialog, in the docs and the implementation, everything was >>> consistent. The docs always said returns a handle or 0. There, in >>> the pointer2string() function, I resorted to testing for null and >>> returning exactly 0 if the handle was null. This will still present a >>> problem down the road when I want to convert everything to using >>> .Pointer objects. But, I figured I would deal with that later. >>> >>> I noticed that in the unix RexxUtil version you have converted the >>> semaphore and mutext semaphore function to the new API and are using >>> uintptr_t for the handles. >>> >>> I could do the same for the Windows RexxUtil functions. Then a null >>> handle would be 0 in the Rexx code. It still leaves the problem of >>> the functions that were documented as returning the empty string. >>> >>> Or, I could do the same as I did in ooDialog, test for null and return >>> 0 or the empty string as appropriate. >>> >>> -- >>> Mark Miesfeld >>> >>> ------------------------------------------------------------------------------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> vendors submitting new applications to BlackBerry App World(TM) will have >>> the opportunity to enter the BlackBerry Developer Challenge. See full prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oor...@li... >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |