It seems that GT.M's %RO utility unconditionally strips trailing spaces from routines when exporting them. Was there a reason this was done? (To be compatible with other MUMPS implementations, perhaps?) The default behavior is causing problems when trying to export VistA FileMan routines out of GT.M. (See http://medsphere.org/message/1255\)
Would it be possible for %RO to ask if trailing spaces should be stripped, like it asks if comments should be stripped? Thanks in advance...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I received an error when I attempted to access the URL in your message. While the reason ^%RO strips trailing white space unconditionally is lost to the mists of time, I suspect it was because that would appear to be unconditionally correct for MUMPS code on all MUMPS implementations. Do you have a counter example?
In any case, part of the reason the utility programs are shipped as source code, even when GT.M is not licensed under a FOSS license, is so that they can be adapted to individual needs.
-- Bhaskar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SourceForge included my ) at the end of the URL. Just remove the ) and it should work.
According to George, "The result of thiese erroneous lines in the cache.dat distribution is that, when you load and run the cache.dat, you see prompts throughout VistA that look like this:
Select OPTION:?
There needs to be a space after the colon."
I'm really glad that the %RO's code was available; I was able to patch the routine and work around the problem. However, I am posting here to see if this is something that the GT.M project would consider changing upstream.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that GT.M's %RO utility unconditionally strips trailing spaces from routines when exporting them. Was there a reason this was done? (To be compatible with other MUMPS implementations, perhaps?) The default behavior is causing problems when trying to export VistA FileMan routines out of GT.M. (See http://medsphere.org/message/1255\)
Would it be possible for %RO to ask if trailing spaces should be stripped, like it asks if comments should be stripped? Thanks in advance...
Jon --
I received an error when I attempted to access the URL in your message. While the reason ^%RO strips trailing white space unconditionally is lost to the mists of time, I suspect it was because that would appear to be unconditionally correct for MUMPS code on all MUMPS implementations. Do you have a counter example?
In any case, part of the reason the utility programs are shipped as source code, even when GT.M is not licensed under a FOSS license, is so that they can be adapted to individual needs.
-- Bhaskar
SourceForge included my ) at the end of the URL. Just remove the ) and it should work.
According to George, "The result of thiese erroneous lines in the cache.dat distribution is that, when you load and run the cache.dat, you see prompts throughout VistA that look like this:
Select OPTION:?
There needs to be a space after the colon."
I'm really glad that the %RO's code was available; I was able to patch the routine and work around the problem. However, I am posting here to see if this is something that the GT.M project would consider changing upstream.