It's probably more to do with perl on windows rather than the individual functions like substr and rindex.

If you notice, all of the wallclock timings are quite a bit longer.

ya.. i just did a bit of testing..

length takes 3 wc secs longer in windows

rindex takes 4 wc secs longer in windows

so.. 3 + 2 (4) = 11 wc secs.

29 - 15 = 14 wc secs.

so that means the perl and/or the substr takes 3 wc secs longer in windows.

which makes complete sense .. since the substr2 took 3 seconds longer in windows. so there you have it.

[edit] nm.. if i was right.. then the substr2 would have been about.. 7 seconds longer rather than 3 seconds.

--
jsu

What really bugs me (not sure if this is a windows issue or perl issue) is that process handling is _so_ crap on windows. I keep finding running processes that shouldn't be running as they are never killed properly.

random processes? or just.. perl, explorer, etc processes?

you always get those random programs running after you install programs. like updater programs and spyware. i hate those. you never know what they are actually doing. they could even be backdoors.

--
jsu

No perl processes.

All my perl processes close properly. I've never forked anything on Windows though.. I don't know how to. On Linux, when I run a perl program and have code to set it to run in the background, I always have commands to shut it down through a terminal that the perl script creates. The process disappears with it.

So why would windows keep perl processes running? Maybe its just XP.

--
jsu

Or my code :)