summaryrefslogtreecommitdiff
path: root/op.c
Commit message (Collapse)AuthorAgeFilesLines
* Re: [perl #20798] foo(eval {}) crashes Perl 5.8Adrian M. Enache2003-03-091-2/+1
| | | | | Message-ID: <20030306221203.GB13330@ratsnest.hole> p4raw-id: //depot/perl@18860
* [PATCH] assertionsSalvador Fandiño2003-03-041-1/+7
| | | | | | | | | | Message-ID: <3E566138.4090709@yahoo.com> and the complement : (with added comments) Subject: [PATCH] bug in ext/B/t/deparse.t Message-ID: <3E563E16.7060303@yahoo.com> plus perldiag.pod patch for the new warning (previous change was, once again, empty) p4raw-id: //depot/perl@18828
* Fixes bug #15654 bizarre constant mangling in 5.8.0Artur Bergman2003-03-041-0/+12
| | | | | | | | | | | | What happened was that a constant was freed, the pad released but the pad slot still held the SV, when pad slot was reallocated to be a target for a stringify, it did a sv_setpv on the target and the original SV was wiped out. When this SV was later on to new places using the constant, they got the wrong value. By replacing pad_free with pad_swipe for these cases, we won't have such a problem. (pad_swipe also removes the pointer to the original SV). p4raw-id: //depot/perl@18820
* Update all copyrights to 2003, from JarkkoHugo van der Sanden2003-03-021-1/+1
| | | p4raw-id: //depot/perl@18801
* More variables for change #18776.Hugo van der Sanden2003-02-251-1/+1
| | | | | p4raw-link: @18776 on //depot/perl: 83b43d9236da9ea6e31fd2df2474f4d7f7220a85 p4raw-id: //depot/perl@18777
* [perl #20682] [fix] @- array not visible in s///Adrian M. Enache2003-02-251-1/+1
| | | | | Message-ID: <20030221155014.GB793@ratsnest.hole> p4raw-id: //depot/perl@18776
* Re: [perl #21321] local ${"FOO"} does not workRafael Garcia-Suarez2003-02-251-4/+0
| | | | | Message-Id: <20030223000327.6f0c11fa.rgarciasuarez@free.fr> p4raw-id: //depot/perl@18774
* Use PL_{argv,stdin,stdout}gv to avoid unnecessary gv_fetch calls.Chip Salzenberg2003-02-241-6/+3
| | | p4raw-id: //depot/perl@18763
* add support for assertions. Updated form of:Salvador Fandiño2003-02-161-3/+17
| | | | | | Subject: Re: Did the assertion patch/feature submission get overlooked? Message-ID: <3DE8F439.50402@yahoo.com> p4raw-id: //depot/perl@18727
* Re: [perl #20798] foo(eval {}) crashes Perl 5.8Adrian M. Enache2003-02-161-8/+0
| | | | | Message-ID: <20030215220510.GB893@ratsnest.hole> p4raw-id: //depot/perl@18723
* outdent else-if chain in scope()Hugo van der Sanden2003-02-161-11/+9
| | | p4raw-id: //depot/perl@18722
* restrict PERL_PRESERVE_IVUV to things that should really give anHugo van der Sanden2003-02-161-13/+1
| | | | | | | integer, but extend to runtime. Based on: Subject: Re: [perl #20827] Unexpected scientific notation. Message-Id: <200302120312.h1C3ChS02613@crypt.compulink.co.uk> p4raw-id: //depot/perl@18720
* Better version of change #18648, by Enache AdrianRafael Garcia-Suarez2003-02-041-2/+2
| | | | | | Message-ID: <20030204101533.GA11817@ratsnest.hole> p4raw-link: @18648 on //depot/perl: 7c2549db3c820cf72273bacc18a4e3d2b361563d p4raw-id: //depot/perl@18656
* Fix bug #8760 : cop_line isn't properly restoredRafael Garcia-Suarez2003-02-031-0/+2
| | | | | when a module is loaded at runtime behind the scenes. p4raw-id: //depot/perl@18648
* In any case, never copy this but use the same SV sinceArtur Bergman2003-02-021-1/+1
| | | | | | if we copy we loose the hash we so badly need. For op_const we might still need to copy however. p4raw-id: //depot/perl@18641
* Move SvPVIV out of ->op_sv of METHOD_NAMED into the pad, fixesArtur Bergman2003-02-021-0/+1
| | | | | | threading issue. Should perhaps be a PVOP to save memory, but then we have nowhere to store the hash of the function! p4raw-id: //depot/perl@18640
* Fix a very small memory leak in op_free, by reserving thePaul Johnson2003-01-281-2/+4
| | | | | | | | | case op_seq == (U16)-1 for the compiler backend Subject: Re: Freeing code From: "Paul Johnson" <paul@pjcj.net> Message-ID: <18918.193.134.254.145.1043759589.squirrel@wesley.pjcj.net> p4raw-id: //depot/perl@18599
* %_ (was Re: [PATCH] operation on `PL_na' may be undefined)Nicholas Clark2003-01-071-8/+8
| | | | | Message-ID: <20021226211626.GD284@Bagpuss.unfortu.net> p4raw-id: //depot/perl@18456
* silence another signed/unsigned mismatch warningGurusamy Sarathy2002-12-281-1/+1
| | | p4raw-id: //depot/perl@18357
* Proper fix for CvOUTSIDE weak refcountingDave Mitchell2002-12-141-20/+19
| | | | | Message-ID: <20021210012644.A7843@fdgroup.com> p4raw-id: //depot/perl@18302
* allow evals to see the full lexical scopeDave Mitchell2002-12-021-4/+6
| | | | | Message-ID: <20021124221906.A25386@fdgroup.com> p4raw-id: //depot/perl@18220
* Fix perl bug #17920 : a case of parser coredump.Rafael Garcia-Suarez2002-11-191-0/+4
| | | | | | | | The fix is to disable Perl_block_start and Perl_block_end when the yacc parser has encountered errors. This prevents corruption of the internal stack, at the expense of correctness, but this doesn't matter as the code is unparseable anyway. p4raw-id: //depot/perl@18166
* Re: [perl #17605] strange behaviour (difference between perl 5.6 and perl ↵Hugo van der Sanden2002-11-071-3/+8
| | | | | | | 5.8.0) in the regexp Message-Id: <200211031641.gA3GfOm08609@crypt.compulink.co.uk> p4raw-id: //depot/perl@18118
* PL_curpad == AvARRAY(PL_comppad) alwaysDave Mitchell2002-10-221-1/+1
| | | | | Message-ID: <20021018133640.A19172@fdgroup.com> p4raw-id: //depot/perl@18048
* Happy chainsaw stories; The removal of the 5005 threadsH.Merijn Brand2002-10-191-152/+0
| | | | | Still imcomplete. Configure will follow p4raw-id: //depot/perl@18030
* prototype() didn't warn when used in void context.Rafael Garcia-Suarez2002-10-161-0/+1
| | | p4raw-id: //depot/perl@18020
* Change the warning message "%s trapped by operation mask"Rafael Garcia-Suarez2002-10-031-1/+1
| | | | | to include '' around the op name. Document it in perldiag. p4raw-id: //depot/perl@17973
* Add a new warning, "Possible precedence problem on bitwiseRafael Garcia-Suarez2002-10-031-0/+22
| | | | | | %c operator", triggerred when a bitwise op has a numeric comparison op as child. p4raw-id: //depot/perl@17972
* Re: [perl #17376] Bug Report - our(%)Yitzchak Scott-Thoennes2002-10-021-1/+1
| | | | | Message-ID: <GNdm9gzkgWOS092yn@efn.org> p4raw-id: //depot/perl@17963
* move all pad-related code to its own src fileDave Mitchell2002-10-021-904/+96
| | | | | Message-ID: <20020925234023.A20044@fdgroup.com> p4raw-id: //depot/perl@17953
* Add silly bandaid to stop segfaults on subsequent accesses toAbhijit Menon-Sen2002-10-021-3/+6
| | | | | | the Nullgv returned by gv_fetchpv() in S_scan_inputsymbol() (<$fred>). p4raw-id: //depot/perl@17950
* patch based on:Yitzchak Scott-Thoennes2002-10-011-0/+12
| | | | | | Subject: Re: [perl #17376] Bug Report - our(%) Message-ID: <a6Mm9gzkgK0P092yn@efn.org> p4raw-id: //depot/perl@17949
* Remove package; (Heh heh.)Abhijit Menon-Sen2002-09-291-15/+8
| | | p4raw-id: //depot/perl@17942
* #17931 checked for wrong constantHugo van der Sanden2002-09-261-1/+1
| | | p4raw-id: //depot/perl@17932
* [perl #10021] Fixing bareword usage under strict.pmKay_Röpke2002-09-261-2/+6
| | | | | Message-Id: <8775B355-CCA2-11D6-AADE-000393414688@dolphin-services.de> p4raw-id: //depot/perl@17931
* Re: Advice on coredumpRafael Garcia-Suarez2002-09-261-1/+1
| | | | | Message-Id: <20020918221457.16cb1b43.rgarciasuarez@free.fr> p4raw-id: //depot/perl@17923
* COW for ithreads (was Re: what copies scalars in ithreads?)Nicholas Clark2002-09-081-1/+6
| | | | | Message-ID: <20020906232052.GB901@Bagpuss.unfortu.net> p4raw-id: //depot/perl@17873
* #17747 caused bad free()s with PERL_DESTRUCT by calling newXS()Hugo van der Sanden2002-08-231-0/+3
| | | | | with a NULL subaddr. Fix that, and stop it happening again. p4raw-id: //depot/perl@17763
* Remove pseudo-hashes (complete)Michael G. Schwern2002-08-171-125/+5
| | | | | Message-id: <20020806200510.GC31473@ool-18b93024.dyn.optonline.net> p4raw-id: //depot/perl@17725
* Re: [PATCH@8545] [ID 20000808.005] OP_REFGEN as an lvalueStephen McCamant2002-08-121-1/+0
| | | | | Message-ID: <14963.32943.102669.67625@soda.csua.berkeley.edu> p4raw-id: //depot/perl@17717
* Re: [perl #15898] coredump with variable ourRafael Garcia-Suarez2002-08-081-13/+13
| | | | | Message-id: <20020802234421.11c62fe6.rgarciasuarez@free.fr> p4raw-id: //depot/perl@17699
* Defined-or patch (cleaned up)Brent Dax2002-08-051-2/+6
| | | | | | From: "Brent Dax" <brentdax@cpan.org> Message-id: <000001c234a1$d1ca72c0$6501a8c0@deepblue> p4raw-id: //depot/perl@17682
* Fwd: [ID 20020703.002] bareword processing bug under 'use strict'Kay Röpke2002-07-091-0/+4
| | | | | Message-Id: <184F11EC-9335-11D6-8F80-000393414688@dolphin-services.de> p4raw-id: //depot/perl@17457
* Re: [ID 20020626.011] wantarray() causes clobbering of unrelated vars ↵Hugo van der Sanden2002-07-081-14/+0
| | | | | | | outside the sub Message-Id: <200207081600.g68G0Xw07553@crypt.compulink.co.uk> p4raw-id: //depot/perl@17423
* Integrate maint patches #13474, #13478, #13584, and #16539;Jarkko Hietaniemi2002-07-071-5/+42
| | | | | | | | | introduce the test case of [ID 20020623.009]. Once upon a time #13474 introduced evil coredumps, but now things seem to be better (tried both with and without ithreads). p4raw-id: //depot/perl@17407 p4raw-edited: from //depot/maint-5.6/perl@17406 'ignore' op.c (@14778..)
* Re: [ID 20020626.011] wantarray() causes clobbering of unrelated vars ↵Hugo van der Sanden2002-06-271-0/+4
| | | | | | | outside the sub Message-ID: <200206271058.g5RAwvE29057@crypt.compulink.co.uk> p4raw-id: //depot/perl@17369
* Spurious empty statements.Jarkko Hietaniemi2002-06-151-1/+1
| | | p4raw-id: //depot/perl@17251
* PERL_HASH() casting games so that our hashed data is "unsignedJarkko Hietaniemi2002-05-171-3/+3
| | | | | | | | | char" but old code using just a "char" doesn't need changes. (The change is using a temporary pointer instead of a direct cast to unsigned char* which would blindly cast anything, not just char pointers.) (The problem arose in MacOS Classic, as seen by Pudge, the cure by Nicholas Clark.) p4raw-id: //depot/perl@16656
* Explicit casts due to #16542.Jarkko Hietaniemi2002-05-111-3/+3
| | | p4raw-id: //depot/perl@16547
* Unused variables now that "did you use incorrect case" is gone;Jarkko Hietaniemi2002-04-281-31/+16
| | | | | | and valgrind claims that the savepvn() in utilize() leaks in e.g. lib/blib.t. p4raw-id: //depot/perl@16237
View Lorry Controller Status