On Sunday, January 6, 2002, at 10:21 AM, James Edward Gray II wrote:
Is it a big gain to pre-extend the data structures? With how many
entries?
It's not usually that much of a gain, but you should benchmark it to
make sure.
The allocation scheme perl uses (for both arrays and hashes) is
On Tuesday, January 8, 2002, at 04:04 AM, Dan Kogai wrote:
on 02.1.8 6:12 PM, Ken Williams at [EMAIL PROTECTED] wrote:
* perl itself requires UFS to compile because of this
No it doesn't - see the archives of this list for directions for
compiling on HFS+. It's pretty easy.
When I say
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Dan Kogai) wrote:
My name is Dan Kogai and this is my first time to drop a message
here -- maybe with a good reason.
I just uploaded a module called MacOSX::File, which allows you to
write programs like the ones on /Developer/Tools.
On Tuesday, January 8, 2002, at 04:46 PM, Chris Nandor wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Dan Kogai) wrote:
I just uploaded a module called MacOSX::File, which allows you to
write programs like the ones on /Developer/Tools. You can now copy()
with resource fork
Have you considered adding this functionality into existing File I/O
code (possibly with some new options) instead of adding whole new API?
-Fred
On Monday, January 7, 2002, at 10:17 AM, Dan Kogai wrote:
My name is Dan Kogai and this is my first time to drop a message
here --
Hi Chris. Long time no see.
on 02.1.9 7:46 AM, Chris Nandor at [EMAIL PROTECTED] wrote:
Hi Dan. Two comments:
Okay let me answer one by one.
1. Did you ask [EMAIL PROTECTED] about the namespace? I am not sure
MacOSX is a good top-level namespace.
Maybe I should have and I did think
Now let me answer the 2nd question of Chris
2. Did you look at the modules in MacPerl that do the same thing, with
an eye toward compatability of interfaces?
Yes I did and I did check File::Copy myself as well. As a matter of fact
File::Copy appears to be MacPerl-compliant already. In a
