oorexx-rfes
|
From: SourceForge.net <noreply@so...> - 2009-05-05 15:58:11
|
Feature Requests item #2787342, was opened at 2009-05-05 17:58 Message generated for change (Tracker Item Submitted) made by orexx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=2787342&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: v4.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Encode "address mode" into "parse version" string Initial Comment: With the advent of ooRexx 4.0 a new, important need arises: determining which addressing mode the running Rexx interpreter uses. This is a vital information, if e.g. one writes installation scripts in ooRexx installing native libraries that must match the bitness of the running (installed) ooRexx interpreter. In a posting to <oorexx-devel@...> from 2009-05-01 I presented this planned RFE and suggested encodings of the "address mode" into the "parse version"-string such, that the ANSI Rexx definitions would not be jeopardized. As no objections were formulated in return of this posting, I would suggest to enhance the "parse version"-string in the following manner, which makes it easy to parse the address mode out of it: REXX-ooRexx_4.0.0(MT)_32_bit 6.03 31 May 2009 REXX-ooRexx_4.0.0(MT)_64_bit 6.03 31 May 2009 REXX-ooRexx_4.0.0(MT)_128_bit 6.05 15 Dec 2015 I.e. append the string "_<ADDRESSSMODE>_bit" to the first word in the version string, where <ADDRESSMODE> is a number representing the addressing mode (currently the value "32" or "64"). Such an encoding would allow for the following keyword statement to extract the address mode: parse version ")_" addressmode "_bit" Even if the string may be extended in the future, this pattern would allow for parsing the address mode reliably for good. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=2787342&group_id=119701 |
|
From: SourceForge.net <noreply@so...> - 2009-07-23 19:21:35
|
Feature Requests item #2787342, was opened at 2009-05-05 15:58 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=2787342&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: v4.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Encode "address mode" into "parse version" string Initial Comment: With the advent of ooRexx 4.0 a new, important need arises: determining which addressing mode the running Rexx interpreter uses. This is a vital information, if e.g. one writes installation scripts in ooRexx installing native libraries that must match the bitness of the running (installed) ooRexx interpreter. In a posting to <oorexx-devel@...> from 2009-05-01 I presented this planned RFE and suggested encodings of the "address mode" into the "parse version"-string such, that the ANSI Rexx definitions would not be jeopardized. As no objections were formulated in return of this posting, I would suggest to enhance the "parse version"-string in the following manner, which makes it easy to parse the address mode out of it: REXX-ooRexx_4.0.0(MT)_32_bit 6.03 31 May 2009 REXX-ooRexx_4.0.0(MT)_64_bit 6.03 31 May 2009 REXX-ooRexx_4.0.0(MT)_128_bit 6.05 15 Dec 2015 I.e. append the string "_<ADDRESSSMODE>_bit" to the first word in the version string, where <ADDRESSMODE> is a number representing the addressing mode (currently the value "32" or "64"). Such an encoding would allow for the following keyword statement to extract the address mode: parse version ")_" addressmode "_bit" Even if the string may be extended in the future, this pattern would allow for parsing the address mode reliably for good. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-07-23 19:21 Message: I would recommend a slight change and use a hyphen instead of an underscore between addressmode and bit. This would permit parsing between informational segments in a readable form. For example: For programming purposes, rendering, at present, 32 or 64: parse version ")_" addressmode "-bit" For visual purposes, rendering "32-bit" or "64-bit", at present: parse version ")_" addressmode . "_" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=2787342&group_id=119701 |