Dave Rolsky wrote:
>This is actually more bizarre then just having a leading colon, I think.
As previously mentioned, a leading colon is no good for signalling syntax.
If you want to go that route, pick some other leading character to signal
a native filename. Bizarreness discussed below.
>It m
On Mon, 19 Feb 2007, Zefram wrote:
I found a better way: URI::file can translate between filename syntaxes.
We can specify that the $TZ setting is a Unix-style filename, and it gets
translated as appropriate. On Windows you can do "/c:/etc/localtime"
and the file C:\etc\localtime is used, and "
Dave Rolsky wrote:
>First, I don't want to make these new modules requirements. What I'd
>prefer to do is just load them if they exist and use them. No one (that I
>recall) has asked for Posix or binary file support, so making them
>dependencies seems like overkill.
OK. But it seems a pity tha
On Sun, 11 Feb 2007, Zefram wrote:
Anything that looks like a System V timezone string is treated as such,
via DT::TZ::SystemV. This interpretation overrides some of the zones
and links in the Olson database, and a couple that were in DT::TZ only.
In each case, of course, the overridden names
I wrote:
>Attached is a patch that revises timezone name parsing in DT::TZ.
Except that I forgot to attach it. D'oh. Really attached this time.
After applying the patch you'll need to do a "./tools/parse_olson --clean".
-zefram
diff -ur dttz-0.59/Build.PL dttz-mod0/Build.PL
--- dttz-0.59/Build
Attached is a patch that revises timezone name parsing in DT::TZ.
The changes:
Anything that looks like a System V timezone string is treated as such,
via DT::TZ::SystemV. This interpretation overrides some of the zones
and links in the Olson database, and a couple that were in DT::TZ only.
In ea
