On 29.11.2021 13:59, Rick McGuire wrote: > I don't think it's a good idea to have a language feature that is so tightly > coupled to the tool > used to build the interpreter. Tools change, but language features are > forever. Also, using the > CMAKE_BUILD_TYPE for the value makes it almost impossible to document the > return values, since > with CMAKE, many different build types are possible.
Hmm, I see your point. How about making it an undocumented feature that is only available when the build type/config is not "release" (rather a developer's build). And instead of naming it "config", naming the method CMAKE_BUILD_TYPE to make it unmistakeingly clear that this is development tool (CMake) specific. ---rony > > On Mon, Nov 29, 2021 at 7:44 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at > <mailto:rony.flatsc...@wu.ac.at>> wrote: > > In the past days I have been creating and testing various versions of > ooRexx on various > systems and > have been using .RexxInfo to check about revisions and bitnesses. > > Unfortunately, .RexxInfo does not have a method "config" that would > return "release", "debug" or > "relwithdebinfo", depending on how ooRexx was configured at compilation > time which sometimes is > important to know when debugging and analyzing the behaviour and/or > results. > > Looking at the RexxInfo code it should be possible to have that > information made available. > > If you think this might be a good idea I would volunteer to implement it, > using > CMAKE_BUILD_TYPE in > lowercase. > > What do you think? > > ---rony >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
