Any Ideas?

writeline(1,"I should have read the manual ...")

close(1)

shell "cmd /c echo Hello!! > file.txt"

Append to existing file

shell "cmd /c echo Hello!! >> file.txt"

You can use @macros after the echo and as part of a filename too.

cj

What is your definition of "Self Modifying Code"

To me - self modifying code is this kind of crap ...

code:

---

break on

$x=1 $y=2
shell 'cmd /c echo $$x=$x > prog.kix'
shell 'cmd /c echo $$y=$y >> prog.kix'
shell 'cmd /c echo ?"x + y = "$$x+$$y >> prog.kix'
call "prog.kix"

exit

---

Are you taking issue with perlarsson's example of doing something fundamental like this...

shell 'cmd /c dir.exe *.* >list.txt'

Am I missing something here ?

Shawn.

Let me give some examples:

shell "cmd /c echo Hello @userid!! > greeting.txt"

will create a file called greeting.txt and will contain Hello (your logon id here)!!

shell "cmd /c echo Hello!! > @wksta.txt"

will create a file that is (your computers name here).txt and will contain the text "Hello!!"

changing the > to >> will append your line to a file...

shell "cmd /c echo @userid logged onto @wksta at @time on @date >> \\server\share\monitorusers.txt"

will add "John logged onto COMPAQ002 at 13:55:29 on 2000/04/20" to the end of the file called monitorusers.txt. This file will have each occurance of this action on each line.

I hope this helps. I can give you some examples of self modifying code too...

cj

P.S. Spelling mistake corrected

[This message has been edited by cj (edited 20 April 2000).]

shell "cmd /c echo Hello!! > @wksta.txt"

and writing this...

MD "%userprofile%\desktop\MyFolder"

???

The question really becomes ...

Is there a big, or subtle, difference between writing self modifying code and simply using dynamic, context sensitive environment variables.

Seems to me that there's a big difference !

Shawn.