[Date Prev][Date Next][Thread Prev][Thread Next]
[Search]
[Date Index]
[Thread Index]
Re: [MacPerl] Bug in 'use'?
If you take a look at hash-it.pm, you will notice that it is designed for UNIX
only. My assumption would be that that module that is causing MacPerl to crash.
I can't confirm this however because my MacPerl doesn't crash at all when I
execute the script you provided, but it does stop and do nothing during
hash-it.pm and when I abort the script using CMD-. I get the "death" message you
mentioned below. It stands to reason (at least from my vantage point) that
unix-os based scripts/modules should not execute properly on a mac unless the OS
is var better than I could have imagined. OS X--who knows? Perhaps there is a
robustness issue when dealing with modules that do not consider what platform
they are running on, but apparently not in my version of macPerl: 5.2.0r4 (perl
5.004). Do you have the latest version?
-K
----------
>From: DeRobertis <derobert@erols.com>
>To: Chris Nandor <pudge@pobox.com>
>Cc: DeRobertis <derobert@erols.com>, macperl@macperl.org
>Subject: Re: [MacPerl] Bug in 'use'?
>Date: Thu, Jul 15, 1999, 6:47 PM
>
> At 5:14 PM -0400 on 7/15/99, Chris Nandor wrote:
>
>>You can try BEGIN { open STDERR, ">errorlog" or die $! } at the top of your
>>script.
>
> I've taken the liberty of adding flushing to it, so:
>
>
> BEGIN { open STDERR, ">errorlog" or die $!;
> $| = 1;
> }
> use strict;
> use diagnostics;
> use sigtrap;
> use Net::SMTP;
> require 'hash-it.pm';
>
>
> It did not crash (wow!) and here is what came to errorlog:
>
> # Ambiguous use of {index} resolved to {"index"}.
> File 'MPW:MacPerl Ÿ:lib:Mac:InternetConfig.pm'; Line 501
> # Ambiguous use of {index} resolved to {"index"}.
> File 'MPW:MacPerl Ÿ:lib:Mac:InternetConfig.pm'; Line 503
> # Ambiguous use of {index} resolved to {"index"}.
> File 'MPW:MacPerl Ÿ:lib:Mac:InternetConfig.pm'; Line 509
> # Use of uninitialized value.
> File 'MPW:MacPerl Ÿ:lib:Mac:Types.pm'; Line 68 # (#1)
>
> (W) An undefined value was used as if it were already defined. It was
> interpreted as a "" or a 0, but maybe it was a mistake. To suppress this
> warning assign an initial value to your variables.
>
> Those are not _my_ problem.
>
> But it did cause Hash-It.pm to spit out the following message (it does this
> because Hash-It installs a SIG{__DIE__} handler):
>
>
> Content-type: text/html
> Content-Length: 608
> Expires: Fri, 16 Jul 1999 01:10:56 GMT
>
> <HTML><HEAD><TITLE>Certificate of Virtual Death</TITLE></HEAD>
> <BODY>
> <H1 Align="Center">Sorry!</H1>
>
> This page could not load due to a bug or misconfiguration. Please
> inform the owner or webmaster of this page of this most unfortunate
> problem, along with exact details of what you did, what browser you
> run, what time it occured, and what OS you have. This will certainly
> help get it fixed<p>
>
> <PRE>
> --Hash-it.pm
> Version 1.5.4 (WARNINGS)
> http://www.erols.com/derobert/
> mailto:derobert@erols.com)
> (technical:# h is not of type Handle during global destruction.
> )
> </PRE>
> </BODY></HTML>
>
> I've seen "h is not of type Handle during global destruction." a LOT. And I
> know that if I run the script again, my mac WILL freeze. Time to quit
> MacPerl!
>
>
>
> ===== Want to unsubscribe from this list?
> ===== Send mail with body "unsubscribe" to macperl-request@macperl.org
>
===== Want to unsubscribe from this list?
===== Send mail with body "unsubscribe" to macperl-request@macperl.org