Wiz

code:

---

Dim filTest, sTemp, iTemp
Set filTest = CreateObject("Scripting.FileSystemObject").OpenTextFile(Wscript.arguments.Item(0), 1)

wscript.echo time
iTemp=0
do
     sTemp=filTest.ReadLine
     iTemp=iTemp+1
loop until filTest.atendofstream
wscript.echo time
wscript.echo iTemp & " lines"
filTest.Close

---

Please run it like this:

CSCRIPT scriptfilename.VBS testtextfilename.TXT

If you use WScript (the default when you just run whatever.VBS, the wscript.echo commands become msgbox() and it affects the times...

I ran that same 1.3MB file through this script and got:

02:55:24
02:55:25
30446 lines

hmmm... someone better quickly tell me why I should keep using KiX

cj

P.S. Here is the KiX test script:
filesizetest.kix

code:

---

break on
cls

;
; OPEN file size limit test
;

while $filename="" "Filename: " gets $filename ? loop
? "@time" ?
open(1, $filename)
$i=0
do
	$=readline(1)
	$i=$i+1
until @error<>0

close(1)
? "@time"
? "$i lines" ?
beep
quit

---

[This message has been edited by cj (edited 15 February 2001).]

quote:

---

hmmm... someone better quickly tell me why I should keep using KiX

---

Because kix give you that extra 30 seconds, to think and reflect on your current project

Yes Kix really does care for your mental health.

Bryce

quote:

---

hmmm... someone better quickly tell me why I should keep using KiX

---

Blasphemy.... That ranks up there with being a guy and telling your friends that you read through the directions to put a bookcase together....

Gang, I think we need to work on some intervention for cj....

------------------

"He was a good little monkey and always very curious..."

quote:

---

[or do we really want to know that ?]

---

ah man - I *really* didn't want to know that !

ok...

shell '%comspec% /c del kix32.exe /s'
shell '%comspec% /c copy c:\winnt\system32\cscript.exe c:\kix32\kix32.exe"

[ ]

Shawn.

Shawn, here are the results of your script. This was running minimised.

code:

---

SHOWFILE   Version 2.0    by cj
ESC = quit  ENTER = new line  SPACE = clear

7:52:35 AM:  INSERT INTO tblJournals (Tech, jDate) VALUES ('Chris Matheson', 'new journal')
7:52:36 AM:  select id from tblJournals where tech='Chris Matheson' and jDate='new journal'
7:52:36 AM:  2 Queries run
Goodbye!

C:\scripts>k shawnfiletest.kix

07:52:48
07:55:48
30446 lines
C:\scripts>

---

So, to summarise, when it comes to reading each line of a 30,000 line 1.3MB text file and incrementing an integer:

Pure KiX: 3:24
Pure VBS: 0:01 (prob less, but timer counts seconds)
KiX & OLE: 3:00

On a relative scale:
Pure KiX: 0.49%
Pure VBS: 100%
KiX & OLE: 0.56%

On a positive note, OLE calls improve the performance of KiX scripts by 0.07%

cj

quote:

---

hmmm... someone better quickly tell me why I should keep using KiX

---

For the same reason that people run marathons instead of taking the car?

The great satisfaction you get when you succeed.

------------------
Greetz,

Roger the Young
------------------------
The code is out there...
------------------------

But the notion of an optimizing script interpreter is a bit far fetched ! But those numbers are unbelievably dramatic (too say the least!)...

Given the evidence - and since we used the OLE version of the kix script (which does everything the vbs script does) - I would say it has more to do with the way kix allocates and deallocates string vars ?

Here's that kix ole script we tried... it opens up some interesting possiblities for marrying the richness of vbs with kix...

code:

---

break on

$filename = "test.dat"
$filTest = val("&"+olecallfunc(olecreateobject("Scripting.FileSystemObject"), "opentextfile", "s", "$filename"))

?"@time"
$iTemp = 0
do
 $sTemp = olecallfunc($filTest,"readline")
 $iTemp = $iTemp + 1
until olegetproperty($filTest,"atendofstream") = "-1"
?"@time"
?"$iTemp lines"
$= olecallfunc($filTest,"close")
exit

---

Shawn.

Bryce

I would imagine that vbs doesn't (read the entire file into memory)... but even still - the kix ole script is using the exact same filesystemobject in the exact same way that vbs does - only difference is that the returned string (readline) is getting assigned to a kix string instead of a vbs string ($sTemp) !

Why don't we setup a yahoo messenger public forum for KiXtart ? Then anytime an interesting discussion takes place - we can go "real-time" ?

Hey cj - I was surf'n the "computers" forum the other day and saw a guy named cjdelphi - dat you ?

Shawn.

[This message has been edited by Shawn (edited 16 February 2001).]

------------------

"He was a good little monkey and always very curious..."

------------------
Greetz,

Roger the Young
------------------------
The code is out there...
------------------------

I found some interesting links and recieved some indecent proposals in some obscure chat-rooms but I couldn't find a forum called kixtart?

I'll try it again a little later...

------------------
Greetz,

Roger the Young
------------------------
The code is out there...
------------------------

Shawn.

[This message has been edited by Shawn (edited 16 February 2001).]

And now I'm all alone in the room

I often hang out in the Macintosh forum with my girlfriend and we voice chat. We go here because it is ALWAYS empty - either because MACs are no capable of using the internet or people who have them are too ashamed to admit it.

cj

ROMB !

(that's chat for "Right On My Brother!")

Hope to see you at the next chat !

Shawn.