I refer to your UDF.

It works fine for me with RC1, but not 4.02. Is there anything I should know?

my test script:

code:

---

break on

call "dirplus.udf"

$dir=dirplus("h:\temp", "*.*", 1, 0)

vartypename($dir) ?

for each $thing in $dir
	$thing ?
next

---

the output on RC1 is

code:

---

Variant[]
h:\temp\dilbert.gif
h:\temp\file
h:\temp\file2

---

but 4.02 returns nothing and just exists on the UDF.

cj

does @error equal anything after you run the UDF?

This happens with KiX32 4.02.

I removed them and the script stops working.

cj

cj

I haven't figured out how it works yet, but I see that it calls itself for each subdir?

Now the big test: 30GB/150,000 files...

cj

Yes it calls it self for each subfolder, to accomplish this it uses the global variables $_i and $_temparray as a flag/place holder. one of the first thing the UDF does is check the existence of $_temparray, if is in use it sets a local UDF variable $subflag to equal 1. Since this variable is new for every recursive call the UDF does not preform the final step exits to the parent UDF and continues to build $_temparray.

The only iteration of the UDF that does not have $subflag set to equal 1 is the root UDF, so once all subfolders have been ran, the child UDF's exit, returning control to the parent UDF, stopping at the root UDF, this process is repeated for every folder in the root UDF DIR command and so on and so on.....

Once the root UDF had preformed the DIR command on the root folder, it then checks the $subflag variable, since this is the root UDF, $subflag was never set and the UDF finishes the rest of the script.

did you follow that?

Bryce

cj

About line 116

code:

---

if @error <> 0 and vartype($fso) <> 9 exit(@error) endif

---

I am about to start using the object handle function...

cj