* David Cantrell <[EMAIL PROTECTED]> [2006-05-03 11:00]:
> A. Pagaltzis wrote:
> >Why would this have to rely on PPI at all? To check whether
> >newlines in the file are consistent, you can just scan the
> >source as an opaque of text, no?
>
> A perl source file might have an embedded heredoc, or a DATA
> section at
> the end. Or even something like ...
>
> print "
>
> __DATA__
>
> "; # ha! take that, foolish naive parser!
>
> It might even have binary data, or a non-ASCII character set in
> any of those places, although I'd be prepared to accept that
> that might be bad practice.
Am I missing something, or won’t all of these will cause problems
with Module::Signature? The thing is that it doesn’t matter how
perl sees the file; what matters is how Module::Signature sees
the file, and to my knowledge, the latter does not attempt to
parse the file in any fashion, so neither should the
corresponding Kwalitee metric.
> It does work very well though and I prefer it to fighting with
> the MakeMaker docs to figure out how to get it to install a
> data file in the right place :-)
Perl has language-level support for uuencoding/-decoding data
(check `perldoc -f pack`). You can take advantage of that to keep
your binary data way, way out of harm’s reach.
Regards,
--
#Aristotle
*AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1};
&Just->another->Perl->hacker;
