[Oorexx-devel] Fwd: [Oorexx-bugs] [ oorexx-Bugs-2779503 ] ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll
I'm not too sure what do with this one. There are a number of APIs that have basically no meaning at all in the 4.0 world, and this is one of them. There are others such as RexxTerminate() and RexxWaitForTermination() that were part of the documented APIs. These have been now stubbed off and are nops and are documented as deprecated. The line in the sand we've drawn so far has been to support documented APIs, but if you've used undocumented ones, well, tough. RexxShutdown() falls into the undocumented category. It would be trivial to stub it out and make it a NOP, but there are lots of other undocumented bits that can't really work that way and there will be absolutely no attempt to get them working in 4.0. My gut feeling is we should say no to this requested, but I'm willing to go with whatever the consensus is. Rick -- Forwarded message -- From: SourceForge.net nore...@sourceforge.net Date: Thu, Apr 23, 2009 at 9:29 AM Subject: [Oorexx-bugs] [ oorexx-Bugs-2779503 ] ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll To: nore...@sourceforge.net Bugs item #2779503, was opened at 2009-04-23 23:29 Message generated for change (Tracker Item Submitted) made by guillerme You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=684730aid=2779503group_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: APIs Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jean-Noel Guillerme (guillerme) Assigned to: Nobody/Anonymous (nobody) Summary: ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll Initial Comment: Hi, we have a C++ application using the rexx API. This program uses the function rexxShutdownAPI. It seems this function is not supported in oorexx 4.0. Would it be however possible to maintain it for binary compatibility ? Thanks. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=684730aid=2779503group_id=119701 -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-bugs mailing list oorexx-b...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-bugs -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-bugs] [ oorexx-Bugs-2779503 ] ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll
On Thu, Apr 23, 2009 at 6:50 AM, Rick McGuire object.r...@gmail.com wrote: I'm not too sure what do with this one. There are a number of APIs that have basically no meaning at all in the 4.0 world, and this is one of them. ... The line in the sand we've drawn so far has been to support documented APIs, but if you've used undocumented ones, well, tough. ... My gut feeling is we should say no to this requested, but I'm willing to go with whatever the consensus is. In principle I agree with this, and think we should say no to this specific request based on that. It is the line I intend to take in ooDialog. Although, I did compromise on one specific instance (BinaryAnd) because it had been used through out the doc examples, even though it was not documented anywhere. I'm not 100% set against it in this case, because I'm not very familiar with those APIs. For instance, if it is a case that they used it because in was in a lot public examples, even though not documented. -- Mark Miesfeld -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-bugs] [ oorexx-Bugs-2779503 ] ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll
Crud, I hadn't thought to check in the samples. It is used in one of the samples and was included in the rexx.h header files. I think this one needs to be added back as at least a deprecated stub. Rick On Thu, Apr 23, 2009 at 10:25 AM, Mark Miesfeld miesf...@gmail.com wrote: On Thu, Apr 23, 2009 at 6:50 AM, Rick McGuire object.r...@gmail.com wrote: I'm not too sure what do with this one. There are a number of APIs that have basically no meaning at all in the 4.0 world, and this is one of them. ... The line in the sand we've drawn so far has been to support documented APIs, but if you've used undocumented ones, well, tough. ... My gut feeling is we should say no to this requested, but I'm willing to go with whatever the consensus is. In principle I agree with this, and think we should say no to this specific request based on that. It is the line I intend to take in ooDialog. Although, I did compromise on one specific instance (BinaryAnd) because it had been used through out the doc examples, even though it was not documented anywhere. I'm not 100% set against it in this case, because I'm not very familiar with those APIs. For instance, if it is a case that they used it because in was in a lot public examples, even though not documented. -- Mark Miesfeld -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-bugs] [ oorexx-Bugs-2779503 ] ooRexx 4.0: RexxShutdownAPI missing from rxapi.dll
On Thu, Apr 23, 2009 at 7:32 AM, Rick McGuire object.r...@gmail.com wrote: Crud, I hadn't thought to check in the samples. It is used in one of the samples and was included in the rexx.h header files. I think this one needs to be added back as at least a deprecated stub. Crud My sentiments exactly. I keep seeing things in ooDialog, and even oleObject, where they documented some part of the implementation, rather than just documenting the exposed functionality. I agree, I think we probably should add back a deprecated stub here. -- Mark Miesfeld -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
