kurila 1.18 released
Gerard Goossen
Highlights:
+ New operators "+@+", "+%+", "@+:" and "%+:"
Rationale: Expressive combining of array and hashes.
+ "{ ... }" generated a coderef
Rationale: Easy generation of coderefs.
+ Removed "goto"
Rationale: "goto" is bad.
+ Comma after first argument
Rationale: Consistent syntax function calls.
http://dev.tty.nl/static/kurila/doc/pod/kurila118delta.html
has a more detailed description of the changes.
Known bugs:
+ Documentation
+ Limited platform support
kurila 1.18 is released together with more then hundred modules,
available together at:
http://dev.tty.nl/static/kurila/kurila-bundle-1.18.tar.gz
kurila 1.18 without the CPAN modules is available at:
http://dev.tty.nl/static/kurila/kurila-1.18_0.tar.gz
And should become available on CPAN.
Or use git to get the latest version:
git-clone git://github.com/ggoossen/kurila
Perl Kurila is a dialect of Perl. With Perl 5 as ancestor it has a
solid base, but without the backwards compatibility
requirement of Perl 5, it is free to evolve into new directions.
More information about kurila is available at
http://dev.tty.nl/kurila.html
--
Gerard Goossen
TTY Internet Solutions
http://dev.tty.nl/
Sartak
> + Removed "goto"
> Rationale: "goto" is bad.
goto has two forms. goto LABEL is widely considered to be bad.
However, goto CODEREF is very handy as it gives the user the ability
to have optimized tail calls, among other things. Did you remove this
form as well? If so, why?
Shawn
Gerard Goossen
One of the reason for removing goto CODEREF is that is depends on argument passing using @_.
For tail call optimalization; that is something that the compiler should do
for any tail call without to the need of a special command.
The other use of goto CODEREF as in not to generate a call layer is lost,
but there often is a more better call level indicator like $Exporter::ExportLevel
and I haven't found msising it any problem.
PS. I have set the Reply-To to the kur...@googlegroups.com, please reply
only to that mailing list.
--
Abigail
> > + Removed "goto"
> > Rationale: "goto" is bad.
>
> goto has two forms.
Actually, in Perl, it has three.
> goto LABEL is widely considered to be bad.
Well, if we strictly go by the numbers, Perl is widely considered to
be bad as well. ;-)
IMO, goto LABEL has its uses. I like it that Perl has it. Luckely, I
don't think it'll be removed from Perl anytime soon.
Abigail
Mark Jason Dominus
> For tail call optimalization; that is something that the compiler should do
I agree.
Moreover, anyone dong tail-call elimination with goto &... is
suffering a 4x performance penalty.
As far as I know, there has never been a version of Perl in which
tail-call removal with GOTO &... was faster than the alternative. I
have looked into this more than once, and decided to omit it from
"Higher-Order Perl" for this rason. I can find the discussion on the
HOP mailing list if you care.
Gerard Goossen
Thanks for the information.
Strange that is so much slower, fortunetely I already got rid of it, so
I don't need to investigate it any further.