diff options
| author | Gurusamy Sarathy <gsar@cpan.org> | 2000-04-24 19:01:24 +0000 |
|---|---|---|
| committer | Gurusamy Sarathy <gsar@cpan.org> | 2000-04-24 19:01:24 +0000 |
| commit | a2293a43268c593a8a95d38299057a646f0fb089 (patch) | |
| tree | 515232728afb60307b625135e36ae5a964b30148 /pod/perltodo.pod | |
| parent | 6f611a1a07288b915db6721d056da56a6d688631 (diff) | |
| download | perl-a2293a43268c593a8a95d38299057a646f0fb089.tar.gz | |
more pod nits (from Larry Virden)
p4raw-id: //depot/perl@5939
Diffstat (limited to 'pod/perltodo.pod')
| -rw-r--r-- | pod/perltodo.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod index f22d4737f8..47febc80c2 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -85,7 +85,7 @@ We need regression/sanity tests for suidperl This value may or may not be accurate, but it certainly is eye-catching. For some things perl5 is faster than perl4, but often -the reliability and extensability have come at a cost of speed. The +the reliability and extensibility have come at a cost of speed. The benchmark suite that Gisle released earlier has been hailed as both a fantastic solution and as a source of entirely meaningless figures. Do we need to test "real applications"? Can you do so? Anyone have @@ -161,7 +161,7 @@ Sarathy, I believe, did the work. Here's what he has to say: Yeah, I hope to implement it someday too. The points that were raised in TPC2 were all to do with calling DESTROY() methods, but -I think we can accomodate that by extending bless() to stash +I think we can accommodate that by extending bless() to stash extra information for objects so we track their lifetime accurately for those that want their DESTROY() to be predictable (this will be a speed hit, naturally, and will therefore be optional, naturally. :) |