ActiveState Community Site - activeperl - Comments

lanch installation

webkamelo_yahoo — Tue, 04 Nov 2008 11:24:53 +0000

file installer do not lanching automaticly
msi do not start

Probably windows command

San — Mon, 18 Aug 2008 12:18:31 +0100

Probably windows command prompt don't like white space in file names unless you encase them in quotes, but talking to your database via command prompt is not very secure anyway. Can you not get the output from within your script using DBI?

Reading output logs

Arctific — Wed, 31 Oct 2007 16:37:26 +0000

In UNIX I can run the following

$result = system("$sql_cmd > $output_file") ;
if(!open(SQL, " < $output_file ")) {
print "Error: output file not opened\n" ;
exit 1 ;
}
#
### Process file should happen here... but does not.
#

Why does this not work in Windows?
A) File exists.
B) Even a for loop trying to make successive open's does not work.
C) Files quoted well, all backslashes accounted for.

What can I do to make this $output_file visible to windows?

Best Wishes,

Don Turnblade
MS, CISSP

DST and ActiveState::DateTime

kevinw — Thu, 01 Mar 2007 00:45:14 +0000

According to one of the developers, the ActiveState::DateTime module is believed to be DST compliant:

It doesn't do any explicit DST calculations itself, so in that way
it is compliant. There may be problems in the code itself, e.g.
how it calculates the difference to GMT at the exact point when DST
is switched on or off in either of the zone, but this may be true
for much of date/time software out there. It is also possible that
the algorithm is perfectly fine too.

Cheers,

kjw

Does this mean

akumarna — Fri, 23 Feb 2007 10:56:24 +0000

Does this mean ActiveState::DateTime module is DST compliant?

Problem fixed

gisle — Wed, 29 Nov 2006 11:28:43 +0000

As of ActivePerl 818 this should not be a problem as ppm will unset this environment variable by itself before it tries to load up Tkx.