>We're talking about how we'll write Perl 6 programs, not PDL programs. We
>need to ensure that the syntax we create is Perlish.
Aggreed.
But there is nothing wrong with making the syntax user friendly, or am I
totally missing what perl is?
Why do we have qw()?
Why do we have "=>" as an alias for comma (at least most of the time)?
Why doesn't perl force us to use paranthesis when calling functions?
etc. etc.
>It needs to fit in with
>the rest of the language--our proposals won't get through if programs look
>quite different in sections just because arrays in those sections have an
>extra dimension.
Which array?
>Creating a 'user friendly' data-crunching language should not be about
just
>catering to Matlab users, or those needing to implement FFTs... I hope
that
>we can make Perl more useful for all the people who have to analyse their
>web logs, or summarise their customer segments, or review survey results,
or
>any of the many things Mere Mortals want to do. Effective array notation
in
>Perl should make these things easy, fast, and intuitive to Perl users.
In general we can say "data mining" I guess. It will be great more people
will switch to perl from these areas and I think perl is the perfect
choice. Genome people are already using perl in some areas.
By the way any decent implementation of analysing their web logs, or
summarising their customer segments, or reviewing survey results will
require tools such as SVD, FFT and other similar transformations.
Baris.
