versioned runtime arx's would be useful if the dev team wanted to do so

I'm thinking it would be ok if the arx was OpenDCL.17.0123.arx or whatever to allow multiple runtime versions within a session.
Its so easy to distrib the runtime, since it (and ENU folder) can be copied to a support path, that its easy to implement on the user end.
The dev team might hate or like this idea, throw it out if its more work than less.
The advantages for users is we could upgrade past projects incrementally, thus allowing us to ues and test the latest for any projects under development.
The other thing is sooner or later, two vendors will be selling tools on different odcl versions, and the users will be stuck choosing one runtime version, thus preventing both from running at same time.  Its the same old dll hell scenario.
Did I get this wrong though?  I know you can reg the arx to run without being in the support path, but cannot run two odcl arx's at once, since they are the same name.
Maybe the function names would overlap though, so its a mute point.  Curious what the recommended procedure is for two compiled tools that each want a different odcl version.
thx

It's not possible to use two different runtime versions simultaneously. Now that the runtime has become more ubiquitous, it cannot be allowed to break older programs (i.e. code written for OpenDCL 6 must work in all future runtimes). There is really no other solution.

is there a way to warn the user that a particular program wants a particular ODCL runtime?
I know I can hardcode it into my lisp, but what if i got confused, and had some odcl.lsp files and wondered what version they were for?  Is the odcl file tagged with anything implying its version?

There is not currently any way to do that, but it's an interesting idea. One problem is that .odcl files are not versioned at the file level, so there is no clear parallel between .odcl file and runtime version. It's really the lisp files that would need to be versioned.