Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
raiph
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
46 ms
·
331.
▲
by
raiph
11y ago
Right. Imo Perl 6 ought to be fairly easy to learn -- the basics are simpler than Perl 5 for example -- but several parts, of which doc is one, are still weak enough that this simplicity is currently obscured. If you're interested, I&#
332.
▲
by
raiph
11y ago
(Edited to say "regular folk" instead of just "folk" in the last paragraph to make it clear I'm talking about non-expert coders who would much prefer that stuff like converting mixed case text to all lower or upper
333.
▲
by
raiph
11y ago
Here's one I've started to focus on in the last few months: say "ปฏิบัติจริง".chars; # says 7 [1] Perl 6 may be a game changer in years to come among those who need to munge text that's Thai, Chinese, etc.
334.
▲
by
raiph
11y ago
The Synopses are intended for compiler writers. The writing intended for users is at http://doc.perl6.org .
335.
▲
by
raiph
11y ago
Right. Aiui both Python 3 and Perl 6 allow correct handling of Unicode byte buffers and whole strings. Which will be great for applications that don't need to do anything at substring or character level. Afaict, in Python 3, code that
336.
▲
by
raiph
11y ago
It may be instructive to consider what exactly you mean by "correct unicode handling". What would you say is the length of the Thai word ปฏิบัติจริง ? What does Python 3 think is the length? What does Perl 6 think is the length? C
337.
▲
by
raiph
11y ago
Note that Inline::Python for Perl 6 allows one to do likewise with Python. [1] "even PyQt's low level mingling finds all the information it needs and we can write programs using PyQt in Perl 6 :)" [1] https://githu
338.
▲
by
raiph
11y ago
> Migrating a relatively complex project from 5 to 6 is extraordinarily hard. Are you willing to share any details of the project you migrated?
339.
▲
by
raiph
11y ago
Have you tried it this year? In his three minute lightning talk in October last year[1] nine demo'd the small things I think you're talking about (calling Python code from within Perl 5 code from within Perl 6 code and using XS-ba
340.
▲
by
raiph
12y ago
= About Python regexes = Aiui "The Future of Python Regexes" SO answer at http://stackoverflow.com/a/7066413/1077672 written by regex (and Perl) expert Tom Christiansen (and last updated by him in 2012)
341.
▲
by
raiph
12y ago
> All of which led to fewer modules being added to, or updated on, CPAN. That's a compelling story. Lots of folk believe it, including, it seems, you. But have you checked your sources and data? For those interested in data and iron
342.
▲
by
raiph
12y ago
The P6 design supports both hygienic and non-hygienic macros because they concluded there were strong use cases for both. I think the Rakudo devs implemented hygienic macros first because they were expecting them to be more difficult than n
343.
▲
by
raiph
12y ago
A comment on Ovid's blog post says: > Perl 6 does some compile time type checking but it only works in some very simple cases. I was thinking that all P6 code had static types that were checked at compile-time and some code, not muc
344.
▲
by
raiph
12y ago
Perhaps you're aware that one of the biggest influences on P6 was Haskell and the 2005-2007 Audrey Tang / Pugs / lambdacamels era. Loads of crazy smart kids sharing wild thoughts with Larry, Damian etc. and writing the first
345.
▲
by
raiph
12y ago
> It's likely such a surprise for him because perl5 was pretty much not even parseable to tell such things. Jonathan got an honors degree from Cambridge University in CS specializing in compilers etc. If you pay attention to his sli
346.
▲
by
raiph
12y ago
They deliberately forgot to steal the syntactic part. :) The P6 project assumed it's possible to create hygienic lisp style macros without homoiconicity. In fact it's always been known that it's theoretically possible to crea
347.
▲
by
raiph
12y ago
Perl 6 feels dynamic but aiui its functional pieces are statically typed checked and statically call resolved unless a dynamic constraint is used. (See another of my comments in this thread for more on that.) Aiui method calls are staticall
348.
▲
by
raiph
12y ago
Right. I think it's reasonable to say that all P6 code is statically typed, using nominal typing.[1] I've not actually checked the following code yet. I just wanted to post it now and will return to update after I've tested t
349.
▲
by
raiph
12y ago
It sounds like the feature you're highlighting here is static checking at compile-time of how routes are going to resolve at run-time. Is that right? Afaict Perl 6 covers this case: http://jnthn.net/papers/2015-fos
350.
▲
by
raiph
12y ago
I've heard that, on modern cpus, with the first 100 or so primes cached, for all but the most performance sensitive applications, MR can be run with sufficient accuracy that there's a greater likelihood that a stray neutron will f
351.
▲
by
raiph
12y ago
Perl 6 elegantly blends static nominal typing and arbitrarily loose or tight dynamic constraints. The following slides were published a week or so ago and should demolish most folks' overly simplistic view that one or other is best or
352.
▲
by
raiph
12y ago
cf the Perl 6 community module for parsing URIs which features Perl 6's unique unification of regexes and grammars: https://github.com/perl6-community-modules/uri/blob/master/l...
353.
▲
by
raiph
12y ago
Perl 6 unifies "regexes" and recursive descent grammars at the syntax level and then compiles them to a hybrid of DFAs, NFAs, and regular code as necessary. The idea is to maintain the simplicity of simple regexes and of parser co
354.
▲
by
raiph
12y ago
Perl 6 unifies "regexes" and recursive descent. See https://news.ycombinator.com/item?id=9039680 or, say, https://github.com/Mouq/json5/blob/master/lib/JSON5/Tiny/
355.
▲
by
raiph
12y ago
Perl 6 unifies "regexes" and recursive descent parsing: '$10.00' ~~ rx{ \$ \d+ \. \d\d }; my $pat = rx{ \p+ \q**2..Inf }; 'pqqpqq' ~~ rx{ <$pat>**2 } Note that these "regexes" are syn
356.
▲
by
raiph
12y ago
No. The Yo-Yo problem was one of the primary themes of ECOOP 89, the European Conference on Object Oriented Programming from 26 years ago. https://en.wikipedia.org/wiki/Yo-yo_problem
357.
▲
Getting beyond static vs. dynamic [pdf]
(jnthn.net)
3 points
by
raiph
12y ago
|
0 comments
358.
▲
by
raiph
12y ago
A much better explanation that I could possibly give, hot off the press: http://jnthn.net/papers/2015-fosdem-static-dynamic.pdf
359.
▲
by
raiph
12y ago
Thank you for replying. my Int $age = 40; $age = "old"; That will generate a compile-time error. (Because the "old" bit is a string literal which is interpreted in this case as being of nominal type Str
360.
▲
by
raiph
12y ago
Make sure you also look at the design document section titled "Multiple constraints": http://design.perl6.org/S12.html#Multiple_constraints It concludes with: > As a first approximation for 6.0.0, subsets of en
More ›