Christian Soeller wrote:
> > Very little discussion was generated by this RFC. Several people noted that perl
>-de 42 and the Perl shell psh already provide some
> > of what the RFC requests; this is noted in the RFC.
> >
> > The RFC is not being withdrawn, since 2 other people expressed (mild) interest in
>it.
>
> I'd like to add that multiline shell capabilities would be *extremly*
> useful for the perldl shell
Well, the psh shell could use some additions, too. Right now psh does
some rather
primitive parsing for completeness of a line and has to guess wether
some input
is intended to be Perl or e.g. calling of an executable or whatever. To
be more specific, the functionality we could need is.
- Determine wether an expression could be a complete Perl expression
(that means, no more open braces, qq blocks etc.)
- The ability to check via the symboltable wether a certain core
function exists without using a hard coded list, as well as gaining a
string representation of their prototypes
- Syntax checking perl code without forking and execing a new perl
instance with -c
- Ability to store and later retrieve all eval sideeffects like
$1,$2,... current package etc. without handling every variable/condition
yourself.
One could argue that we should use the existing parser modules to gain
the necessary information as far as possible, on the other hand these
facilities are already there somewhere, hidden in the Perl executable.
I have to admit though that I somehow doubt that only one
applications(psh and perhaps the perldl shell, too) justifies such
additions to perl.
--
Markus Peter - SPiN GmbH
[EMAIL PROTECTED]
