Add a /b switch to the kix32 command line for running scripts in AT scheduled batch mode ( under "system account" ).

If KiX can be told that there is NO user context, this should clear-up those annoying eventlog errors !

Shawn.

real, byte, boolean etc...

cj

1. Compile Kix to an .EXE (see CJ comment)
2. A working md command that I can create multilevel directories (like d:\1\2\3\4) without using shell "cmd /c md d:\1\2\3\4"

For the rest congratulations Ruud.

you get

dim $array[2]=(var1,var2,var3)

...or something like that!

Regards
Doug

Add a parameter to DIR() to return filenames in an ordered form (ordered by filename,modification date)

Use an environment variable (KIXPATH?) to locate .SPK .WAV .TXT files and CALLed .KIX scripts.

Persistant (static) local variables in different scopes - I've created a couple of library routines which are called from various scripts. I'd like to make them totally modular, but I need to keep some variables between calls. The only option currently is to use variables in the GLOBAL scope, which means of course they can be modified by the calling script or another called script.

Richard.

[This message has been edited by rhowarth (edited 15 June 2000).]

dim $myarray[10,2]

cj

But then again, is it really much an issue if you implement a system of always downloading the logon files to the client and then executing locally thereafter.

Ok seriously I think Kixtart needs two things the most:

1) The ability to pass and return variables from functions. This would allow for us all to start sharing functions and building Kixtart libraries.

2) More advanced data structures (how about a class? wooohoo..)

3) Console-less execution

4) Possible ability to compile scripts to exe

With these in place, we could just about fill in the rest of the functionality ourselves without modifying the base interpreter.

------------------
K Torkelson
Sys Admin Analyst
ktorkelson@providentfunding.com

Henri

I gotta face the facts....I'm a dreamer

------------------
Cheers....

David

Single line IF statements.!

For example, how many people here need to use three lines to map a printer for a group...

code:

---

IF INGROUP("DPF01")
   USE LPT3 "\\PRT_HO_SVR\DPF01"
ENDIF

---

Would it not be nicer to have...

code:

---

IF INGROUP("DPF01") THEN USE LPT3 "\\PRT_HO_SVR\DPF01"

---

It would mean that all those printer mapping scripts would be 1/3 smaller.!!

Just a thought

Wiz

[This message has been edited by Wizard (edited 19 February 2001).]

IF INGROUP("DPF01") USE LPT3 "\\PRT_HO_SVR\DPF01" ENDIF

this is 1 line, ain't it?

wiz

As an example i have used the following many times.

shell '%comspec% /c program.exe > "$tempFile"'
$nul = open(1,$tempfile,2) $return = readline(1) $nul = close(1) del $tempfile

That is 2 lines containing 5 different commands.

Bryce

[This message has been edited by Bryce (edited 19 February 2001).]