> Lee responded to my earlier question:
>
> > > Question is - why the h-ll does a null-routine/function like that
> > > cure the Program Error?
> >
> > Sound wierd: can you send in and cc me the minimum that causes
> > the situation?
>
> At the moment I can't as it's part of a 3million UKP project covered
> under a NDA :-(, but what I can say is that I've got a main library
> file that's currently 46Kb which is required() by each script measuring
> around 1-2Kb. It's only recently (past few weeks) that this problem
> has been noticeable so I'm willing to put it down to hardware failure,
> but on the other side of the coin this is a bigish project (designed
> to handle in excess of 2 terabytes of data spread across multiple-systems
> blahdy blahdy blah).
I did one of these a couple of months ago: boring ;) You really shouldn't
put it down to hardward, youknow, as next month it'll get worse ;)
Did you go for a big night out a couple of weeks ago...?
> I'll see if I can produce a small sample that causes the problem, but
> I was wondering if anybody else had experienced a similar problem...
Not here. Have you done a text search of all your files - grepped any
calls to the null function?
> > Hell of a .sig you got there.
>
> Not mine - it's added by the company mail server so there is 'no'
> way of bypassing it...
Go freelance; if we all stick together, we can get rid of such clutter
as that .sig and, oh, Visual Basic....
If you can cut out most of the files, and leave the min that causes
the error....do post.
_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
