On Wed, Jun 25, 2008 at 1:11 PM, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 01:04:43AM -0700, Moritz Lenz wrote: >> Rakudo as of r28692 reports a slightly wrong context on reporting parse >> failures. >> >> When trying to parse t/spec/S02-builtin_data_types/lists.t (r21012) it >> reports: >> >> Statement not terminated properly at line 118, near "= [EMAIL PROTECTED];" >> current instr.: 'parrot;PGE::Util;die' pc 120 >> (runtime/parrot/library/PGE/Util.pir:82) >> >> But line 118 reads like this: >> my $arrayref = [EMAIL PROTECTED]; >> >> So there's just a single backslash, while two get reported. I see no >> need for extra quoting in the error message. > > What if there's a newline or other special character in the source > at the point of the error? Should those be quoted?
If the error is showing "line 118", then a newline -in the source- isn't going to show up ^_^ I think a better option is probably to escape only non-printables, rather than what I am assuming is just using the parrot default of escaping for inclusion into another string. > Pm > -- Will "Coke" Coleda
