From: "Carlo Hogeveen" 
@Date: Sun, 23 Feb 2003 15:39:17 +0100
@Sender: semware-owner{at}sawasdi.apana.org.au





Put one of the following lines at the end of your Main() procedure
and your troubles are over:

PurgeMacro(SplitPath(CurrMacroFilename(), _name_))

or

PurgeMacro("mymacroname")




> -----Original Message-----
> From: tsepro-bounce{at}freelists.org [mailto:tsepro-bounce{at}freelists.org]On
> Behalf Of Fred Holmes
> Sent: zaterdag 22 februari 2003 20:03
> To: tsepro{at}freelists.org
> Subject: [TSEPro] Running a just-compiled macro repeatedly
> 
> 
> 
> If I code, compile, execute/test a macro repeatedly, I must each time purge 
> the macro before running the next iteration.  If I don't, executing the 
> macro executes the object code that TSE had kept in its own memory space 
> (I'm guessing), rather than reading the new object code from the 
> just-written .mac file on disk.  Not only is it a pain to remember to purge 
> the macro, it's extra mouse-clicks as well.  And when I really forget, I 
> think the newer code isn't working, when the real case is that it's the old 
> code that's running again and failing.
> 
> Is there any way to hook the compilation of a macro (compiled through 
> Ctrl-F9) to automatically purge the old macro at the time of 
> compilation?  (I would think that this would be the default mode of the 
> editor anyway?)  Some other good solution?
> 
> Thanks,
> 
> Fred Holmes
> 
> --
> TSEPro Mailing List
> List Maintenance: www.semware.com/html/list.htm
> 
> 
--
TSEPro Mailing List
List Maintenance: www.semware.com/html/list.htm



---
[sawasdi.apana.org.au] (3:800/846.13)