Is there any other way to find out? I also have this need occasionally

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 29.11.2021 um 13:59 schrieb Rick McGuire <object.r...@gmail.com>:
> 
> 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. 
> 
> Rick
> 
> 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 <mailto:Oorexx-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to