Micronetics M was the same way. I used an outside editor to edit files and it had a load function.
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com
http://opensourcevista.net:8888/NancysVistAServer/WVEHR-VOE1.0-Install-Cache/
--
Nancy Anthracite
Sent on the Sprint® Now Network from my BlackBerry®
On 04/13/2011 10:38 AM, OldMster wrote:
> Kevin,
> If you are going to be switching back and forth between Cache/GT.M, I
> highly recommend you look at Serenji from George James Software. You
> can use it for both Cache and GT.M, and provides syntax checking,
> debugging, etc. consistently across both.
>
> Namespaces are wonderful things, and I keep nagging Bhaskar to provide
> something similar in GT.M, (without much success).
[KSB] What do namespaces give you that $zroutines and $zgbldir together
do not? A MUMPS process needs to locate its routines and it needs to
locate its global variables. $zroutines & $zgbldir are GT.M's way of
providing that access, and other MUMPS implementations evidently use
namespaces for the same purpose.
Regards
-- Bhaskar
> You really don't have to worry about them too much if everything you do
> is in single namespace, which I believe is the case for Vista. Think
> of a namespace definition as your global directory file created with
> GDE, and you'll be close enough to work with. Since Cache is not a
> daemonless like GT.M, it has to know about ALL the global directories,
> not just the one the current process is using. Incidentally, GT.M is
> the only M implementation I know of that doesn't have some mechanism
> like namespaces.
>
> Where routines are stored is a little more tricky. Cache has 2 kinds
> of routines - .MAC routines and .INT routines. .INT routines are
> traditional M routines, and only M syntax is allowed. .MAC routines
> allow you to use Cache Macros (stored in .INC) and embedded SQL. Cache
> compiles the source into 'Object' routines that have a .OBJ extension.
> .MAC routines are stored in the ^rMAC, Object is in ^rOBJ, Macros are
> in ^rINC, and .INT routine are in ^ROUTINE.
>
> When a .MAC routine is compiled, it converts all the embedded Macros
> and SQL into standard M code, generates a .INT, and then generates a
> .OBJ from that. Whether or not the .INT is actually retained in the
> ^ROUTINE global is a switch that is passed to the compiler (and is an
> option selection in Studio/Serenji).
>
> Mark
>
> --
> http://groups.google.com/group/Hardhats
> To unsubscribe, send email to Hardhats+u...@googlegroups.com
--
GT.M - Rock solid. Lightning fast. Secure. No compromises.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________
Regards
-- Bhaskar
--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com
Right click on the cube, choose Studio, click on change namespaces, and then
click on the namespace you want. The then click on Open and the dialog box
appears. Choose .int routines and put the name of the routine you want to
work on in there. Wild cards are OK to help you search. That will load the
routine. Edit it and save and it will compile.
--
Nancy Anthracite
In the VA most of the developers I knew used the cube and like I said there are certain features that are really nice, like the different colors. VPE is another good choice. And as Sam mentioned ZZMKEDIT, the one I use. I have used on GT.M but for some reason it fails to kill off ^TMP("DDWRTN" after filing the routine, but since I only edit a routine on GT.M once or twice a year I have never dug into the bug. btw that global node is used to prevent two people from editing the same routine at the same time.
To port routines without using KIDS you can do a ^%RO on the source and ^%RI on the target, just remember to run DOS2UNIX on the file.
jlZ
> --
> http://groups.google.com/group/Hardhats
> To unsubscribe, send email to Hardhats+u...@googlegroups.com
>
--
hiybbprqag