On Fri, 6 Sep 2002, Steve Fink wrote:
> > > - Make sure P6C::IMCC::code() adds a newline after every line
> > > (I was getting two consecutive lines of code smashed together)
> >
> > This will probably make the output pretty ugly. I'd rather find the
> > culprit for the smashed-together lines, or only add a newline if there
> > isn't one already.
>
> The behavior before this patch seems inconsistent. It unconditionally
> appends a newline to the end of every line in the passed-in array
> except for the last one.
You're right -- it's sort of trying to do two things -- append an array of
line (adding newlines), and append a chunk of code as-is. Unfortunately,
it doesn't work for the former, and since I typically haven't used it that
way, I've never noticed the lack. Typical usage is
code(<<END);
lines of pasm
go here
END
so adding newlines is not useful in the common case.
> I'm very impressed by P6C. This is the first time I've looked at it
> seriously (I'm trying to do the languages/regex integration),
Glad you like it, though now that you're doing regexes, I'll have to stop
playing around with them, I guess :(. Do you have any plans to port
languages/regex to the Rx ops and/or port them to it? As for the
eval/autoload bit -- what particular parts are a problem?
> Bug report: perl6 -e 'print 1 if /a/' calls P6C::IMCC::rule::val(),
> which does an rx_popindex immediately and runs out of stack.
Hm... That's probably not the desired behavior, but '$_' is only
implemented for given/when (and maybe a couple of other places), so it's
not too surprising that badness occurs.
/s
