New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perl 5.005_62 and Win32::OLE 0.1101 #839
Comments
From gustav@morpheus.demon.co.ukBuilding Win32::OLE 0.1101 with Perl 5.005_62 (NT4SP5, VC6SP3) I The test uses Excel, and I have Excel 2000 installed, so there The only nontrivial code I can see which is run when the module is I put a croak() at the start of the _Typelibs() code, and the I now don't know what is likely to be the problem... Some other notes: 1. PERL_INTERNAL_GLOB requires my Win32 patches. Otherwise, 2. My initial build had Sarathy's STOP block patch and my 3. I rebuilt with USE_BINMODE_SCRIPTS removed. That made no Perl Info
|
From @janduboisOn Wed, 10 Nov 1999 21:46:46 -0000, "Paul Moore"
Please don't send bug reports for non-core modules to p5p but to the
The error happens during compilation of the Win32::OLE::Const module. The perl -e "sort{my $c;return $a <=> $b}(1,3,2)" but don't have time to investigate this further right now. It is case OP_RETURN: -Jan |
From @gsarOn Fri, 12 Nov 1999 20:53:51 +0100, Jan Dubois wrote:
This looks like something I fixed a few weeks back. Sarathy Inline Patch-----------------------------------8<-----------------------------------
Change 4417 by gsar@auger on 1999/10/20 23:45:03
avoid coredump on C<sort { my $c; return $a cmp $b } ...>
Affected files ...
... //depot/perl/op.c#204 edit
Differences ...
==== //depot/perl/op.c#204 (text) ====
Index: perl/op.c
--- perl/op.c.~1~ Wed Oct 20 16:45:08 1999
+++ perl/op.c Wed Oct 20 16:45:08 1999
@@ -6187,7 +6187,7 @@
break;
case OP_RETURN:
- if (o->op_next->op_type != OP_LEAVESUBLV) {
+ if (o->op_next && o->op_next->op_type != OP_LEAVESUBLV) {
o->op_seq = PL_op_seqmax++;
break;
}
End of Patch. |
From @janduboisOn Fri, 12 Nov 1999 14:47:09 -0800, Gurusamy Sarathy
Yes, it's exactly the same. I'm surprised I reduced the problem from I just wasn't sure if simply checking o->op_next for NULLness was the -Jan |
Migrated from rt.perl.org#1767 (status was 'resolved')
Searchable as RT1767$
The text was updated successfully, but these errors were encountered: