develooper Front page | perl.perl5.porters | Postings from December 2013

[perl #119593] Bleadperl v5.19.3-296-gffdb8b1 breaks BAREFOOT/Test-File-1.34.tar.gz

Thread Previous | Thread Next
bulk88 via RT
December 22, 2013 18:18
[perl #119593] Bleadperl v5.19.3-296-gffdb8b1 breaks BAREFOOT/Test-File-1.34.tar.gz
Message ID:
On Sat Dec 21 20:25:13 2013, bulk88 wrote:
> On Sat Dec 21 18:07:08 2013, sprout wrote:
> >
> > Could someone else familiar with ops review my suggestions?
> >
> > Should I
> > • make all ops store line numbers, fixing numerous bugs and
> >   increasing memory usage,
> > • introduce a new SUBOP op type that includes a line number or
> > • make PL_copline localisation only protect the inner value, not
> >   the outer?
> >
> I suggest won't fix. IMO line numbers are on a statement, not
> expression/substatement basis. None of the suggestions sound like the
> increase in memory or CPU will justify a bug about undocumented and
> subject to change behavior.

I did think of something, what if a single bit in the op struct indicated if this op is on a new line, or previous line. The line number of the current op * is determined by walking from the COP along the the linked list to the current op * and counting the number of newline bits. The algorithm for computing the line number is very overhead intensive/slow, but takes very very little memory, just 1 bit per op struct.

bulk88 ~ bulk88 at

via perlbug:  queue: perl5 status: open

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About