I'm rewriting Querylet, and in the process, I want to add better error messages. The problem is that Querylet is a source filter which translates (for example):

use Querylet;

database: dbi:SQLite:dbname=foo.sqlite
[download]

into

use strict;
use DBI;

my $dbh = DBI->connect('dbi:SQLite:dbname=foo.sqlite');
[download]

This works very well, but if there is a runtime error, say an error in ->connect(), Perl will claim an error in line 4 of the resulting code instead of line 3 of the original code.

What I want to do is add appropriate #line nnn comments (see perlsyn) that match up the line numbers in the generated code back to the line numbers in the original code:

use strict;
use DBI;

#line 3 "test.querylet"
my $dbh = DBI->connect('dbi:SQLite:dbname=foo.sqlite');
[download]

The only, minor snag in this scheme is that I haven't found a way to get at the current offset in the input stream to find out at which offset the current Querylet section starts.

So my question boils down to these alternatives, or a better approach that I completely missed:

• How do I coax Filter::Simple (or Filter::Util::Call) into giving up the current position of their input stream?
• Can I add this functionality though a hook added to @INC instead?
• Is there another approach that I can use instead?

I don't care much for the fragility of the approach, as Querylet likely is the only source filter in action.

Update: As I realize just after reviewing and posting, the offset only needs to work for the first use Querylet; statement, as Querylet transforms the complete rest of the program, passing through everything it does not recognize. I keep track of the line numbers there myself, but I lack the initial offset where the source filter starts.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.