J
jm
perl provides good things and bad ones.
In the good thing, such as:
* it is adapted for text processing
* it is poorly typed
* it is enough powerful with unicode
* provide arrays and hash and reference (and objects)
* transparently manage any kind of numbers.
* is C interfacable
* has basic network and IPC possibilities
* pack/unpack
In the bad things, such as:
* bytes/unicode confusion
* stack overflow within bad regular expression
* memory consumption (might be an issue when energy will be more expensive?)
* insufficient typing
* some portability issue, notably with function «system».
* some $@% issues.
* pack limitation: cannot just modify one byte.
perl6 looks like a cleanup of perl, but I am wondering:
how will memory be handled in perl6?
how will bytes be handled in perl6?
why perl6 encourages complex regex (as x become standard)?
how will perl6 address portability issues?
how will perl6 address IPC issues?
In the good thing, such as:
* it is adapted for text processing
* it is poorly typed
* it is enough powerful with unicode
* provide arrays and hash and reference (and objects)
* transparently manage any kind of numbers.
* is C interfacable
* has basic network and IPC possibilities
* pack/unpack
In the bad things, such as:
* bytes/unicode confusion
* stack overflow within bad regular expression
* memory consumption (might be an issue when energy will be more expensive?)
* insufficient typing
* some portability issue, notably with function «system».
* some $@% issues.
* pack limitation: cannot just modify one byte.
perl6 looks like a cleanup of perl, but I am wondering:
how will memory be handled in perl6?
how will bytes be handled in perl6?
why perl6 encourages complex regex (as x become standard)?
how will perl6 address portability issues?
how will perl6 address IPC issues?