Re: Typing allergy

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from cld@xxxxxxxx (Carl Distefano) on Mon, 5 Jan 2004
23:04:15 -0500

>>> At long last, I have installed RUNCODE on a key.

>> Lord, you can't put every program on a key!

> True, Robert, but if I had to choose one, RUNCODE would be it. I've
> had it on Alt-R forever. Passing args is no big deal: just put the
> arg on the CMline.

Agreed, no big deal -- but argument passing does remain
 "a bit tricky if you load RUNCODE on a key -- you've got to
  mind the command line quite vigilantly"
in other words, you can't just hit that dedicated key without taking care that
either the CMline is cleared or else has a proper argument.

>> RUNCODE is great for snippets and demos and little stuff, but
>> ... you now have three copies in memory (plus the overhead
>> of RUNCODE itself). Thus OOM can loom (Out Of Memory).

> Good point. But for big stuff there's an easy workaround: have
> RUNCODE SAveDeF the block to a file and RUN the file.

Simpler, I think -- my procedure when developing code -- is just to *start out*
with a TMP file, and RUN it. You need a "space" (a window, a file, someplace)
in which to write your code, so why not a TMP file ab initio? When perfected,
or at any rate darn close, I convert the TMP file into a Type 5-frame in U2,
and finish developing in the U2 environment. RUNCODE increases the likelihood
of OOM (in my experience), so I remove it entirely from the equation when
developing "serious code".

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------