13 messages in org.perl.perl5-portersRe: Find the line number of the curre...
FromSent OnAttachments
Tim BunceMay 2, 2007 4:56 pm 
Artur BergmanMay 2, 2007 6:59 pm 
Dave MitchellMay 3, 2007 3:43 am 
Paul JohnsonMay 3, 2007 4:07 am 
Tim BunceMay 3, 2007 4:15 am 
Artur BergmanMay 3, 2007 10:34 am 
Artur BergmanMay 3, 2007 10:49 am 
Tim BunceMay 3, 2007 1:46 pm 
Tim BunceAug 8, 2007 6:13 am 
Tim BunceAug 8, 2007 6:33 am 
Dave MitchellAug 8, 2007 8:33 am 
Tim BunceJul 16, 2008 2:59 pm 
Paul JohnsonJul 17, 2008 2:48 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Find the line number of the current block from XS code?Actions...
From:Tim Bunce (Tim.@pobox.com)
Date:May 3, 2007 1:46:27 pm
List:org.perl.perl5-porters

On Thu, May 03, 2007 at 10:50:07AM -0700, Artur Bergman wrote:

On May 3, 2007, at 4:15 AM, Tim Bunce wrote:

Umm. PL_copline looks like it's compile-time only. And CopLINE(PL_curop) gives the line number of the current statement, not the first statement of the current block/scope.

With a bit of digging the nearest I've seen (or guessed at) so far is CopLINE(cxstack[cxstack_ix].blk_oldcop) which I think will give me the line number of the start of the current subroutine, eval, or loop.

Right?

Loop level would be handy but I'd still like to get down to block/ scope level.

Ah, I missunderstood, you want to find the start of the perl level scope that access your XS?

Yes.

loop is a block/scope :) but I guess you can just walk down the cxstack until you find the type you want

CxTYPE == CXt_SUB and CXt_BLOCK

Ah, yes, I see CXt_BLOCK corresponds with pp_enter which corresponds with entering a block/scope. Great. Obvious when I see it now.

Thanks Artur.

Tim.

p.s. This is in relation to a background project of mine to extend Devel::FastProf to support gathering profile data per-block. I'm not sure it'll happen, but I am sure it would be interesting and useful.