raiph

43 ms·

301.
by raiph 11y ago
> With perl6's grammar support, some folks are working on importing the perl5 grammar into perl6[0]. If someone just wants to run Perl 5 code, especially from CPAN, Inline::Perl5 is the answer, not v5.
302.
by raiph 11y ago
> But the damage has been done @ this point -- a lot of the community has wandered off Do you think the Perl community should have tried to slow down or reverse the exodus?
303.
by raiph 11y ago
Gotchya.
304.
by raiph 11y ago
> I expect that if you try out the Python version on your system you'll also get the "right" answer. I don't think so. In my tests standard python (2.7 and 3.5) ignores grapheme clusters.
305.
by raiph 11y ago
> So apparently perl6 is also "wrong" and operates on codepoints Yes and no. Yes, because the in-development Rakudo compiler is clearly currently giving the wrong result, and no because it operates on grapheme clusters (but has
306.
by raiph 11y ago
And someone else just pointed out that the python line should instead be the two lines: 3 -4 tiny number # python 2 3.5 -3.5 tiny number # python 3
307.
by raiph 11y ago
These aren't codebases but 1-100 LOC solutions to 700+ programming tasks: Perl 5: http://rosettacode.org/wiki/Category:Perl Perl 6: http://rosettacode.org/wiki/Category:Perl_6
308.
by raiph 11y ago
Someone just pointed out that I missed a line in the bit about string length: "ปฏิบัติจริง".chars = 7 # Perl 6
309.
by raiph 11y ago
Continuing after arbitrary computation events that are meant to be fatal seems to me to be asking for trouble. It's why folk reviled Basic for its "On Error Resume Next" command. It has nothing to do with what Perl is about.
310.
by raiph 11y ago
Do you think it will be OK given this law to automatically generate FFI bindings by parsing protectable POSIX C headers? In this instance a human will have invoked a program that literally copied the source in to ram, bit by bit, and then c
311.
by raiph 11y ago
Latest Rakudo responds with a compile-time error: ... Unsupported use of ->(), ->{} or ->[] as postfix dereferencer; in Perl 6 please use .(), .[] or .{} to deref ... Following the advice leads to: my $larry;
312.
by raiph 11y ago
> I think my experience with Perl [is] a bit dated In some ways, contemporary Perl 5 (eg this year's 5.22 release) is quite unlike older Perl 5s. For example Moose -- which first arrived in 2005 -- is a powerful and relatively clean
313.
by raiph 11y ago
I got it even if no one else did. :)
314.
by raiph 11y ago
This is of course what Larry meant, not the literal meaning. The whole Perl 6 thing is the ultimate in this form of lazy; 15 years of design work on both the culture and the technology just so he can die in peace in his old age rather than
315.
by raiph 11y ago
It'll be interesting to c how the radically overhauled module management in Perl 6 pans out. (They're making sure that installation is practical. For example, NativeCall, for calling C libs, does not require a C compiler.) > Al
316.
by raiph 11y ago
> most of the time you're just dealing with code that might have a few sigils preceeding an identifier I personally like sigils but, afaict, one can almost eliminate sigils in Perl 6 if one wants to. Instead of $ sigil on scalar (si
317.
by raiph 11y ago
> [lang X] doesn't handle [basic math] correctly among other things. From a recent talk[1], what are x, y, z in the following? x = 7 ÷ 2; y = -7 ÷ 2; z = .1 + .2 - .3 x y z 3.5 -3.5
318.
This week: Unicode 8, loads of fixes, preparing for shaped arrays(6guts.wordpress.com)
1 points by raiph 11y ago|0 comments
319.
by raiph 11y ago
Perl 6 unifies "regexes", PEGs, and lexical closures.[1] [1] https://en.wikipedia.org/wiki/Perl_6_rules
320.
by raiph 11y ago
In Perl 6 the regex character escaping rule is: > Alphanumeric characters and the underscore _ are literal matches. All other characters must either be escaped with a backslash (for example \: to match a colon), or included in quotes. Fr
321.
by raiph 11y ago
From the preamble of the page you linked: > In fact, regular expression culture is a mess, and I share some of the blame for making it that way. Since my mother always told me to clean up my own messes, I suppose I'll have to do jus
322.
by raiph 11y ago
Thanks.
323.
by raiph 11y ago
What do you think of the destructuring features in Perl 6 as discussed for example at http://perlgeek.de/blog-en/perl-6/2013-pattern-matching.html ?
324.
by raiph 11y ago
RNNs wouldn't fall for confusables... ;) The venerable Perl 5 and its ecosystem has long aimed at Unicode compliance with acceptable performance and is one of the best toolkits available in 2015. Perl 6 aims to outdo Perl 5 (and other
325.
by raiph 11y ago
What do you make of NFG, as mentioned in another comment below?
326.
by raiph 11y ago
NFG enables O(N) algorithms for character level operations. The overhead is entirely wasted on code that does no character level operations. For code that does do some character level operations, avoiding quadratic behavior may pay off ha
327.
by raiph 11y ago
> lack of direct engineering visibility -- currently obvious commit sign-offs -- Larry Wall https://github.com/TimToady?tab=activity
328.
by raiph 11y ago
I haven't tried Swift yet but my latest observations and guessing about your grave accent example are as follows. Based on direct cut/paste and inspection, the grave accent (in the "`" string above and here in these pare
329.
by raiph 11y ago
Fwiw, the same (I think) in idiomatic Perl 6: +$path.IO.lines.words
330.
by raiph 11y ago
The example you've provided is confusion/complexity related to what a "character" is. If a language supports a string type and related functions that equate "character" with a grapheme they'll deliver your

More ›