I'd like to note that Hash tables don't preserve the order they're created, and
that this isn't a perl6 thing, this is intrinsic to the definition of hash
tables.
On October 3, 2017 9:06:47 AM EDT, Andrew Kirkpatrick
wrote:
>Thanks, your script enticed me to explore different ways of
>construc
With perl5, that could have been something like. "perl -Mmy -e ...", but I
don't have access to a perl6 at this instant to compare. There should be a flag
you can use to include a module into the.running environment before evaluating
the
"-e" code.
Using "use" within the "-e" string should wor
Thank you! I'd have hated for my echo of your knowledge to be the only tip he
got, and you included a pointer to the option he needed, which I didn't try
from my phone:-)
As for LWP being a pain, I see it differently, filling the specs for a web
client --- many specs --- is a pain. The curl project is trying to wrap a
blanket around that pain.
I just googled perl6 libcurl, and got
https://github.com/CurtTilmes/perl6-libcurl
That's definitely where I'd start.
I'm not expert in curl, nor even http client coding, so I just checked the
curl(1) man page on my system, it says:
-L, --location
(HTTP) If the server reports that the
requested page has moved to a different
location (indicated with a Location:
I think it'd be cool to notice, and properly report, write errors, rather than
silently ignoring them.
Back when lwall was asking for things we wanted perl6 to do, I asked to be able
to wrap builtins specifically so I could
use Fatal qw(print).
Yes, perl5 often ignores write errors, but no, I
Well, tastes can reasonably differ on that point. Bunging all of the
complexity, of implementation, of design tradeoffs, and of documentation, into
one big module might suit some tastes. Not mine, as either an implementor or a
user.
Not all uses need all components, and I for myself would rathe
Well put.
The clearest description of Python's approach I've read, explained it as a
lexer that tracked indentation level, and inserted appropriate tokens when it
changed.
Hostile or not, thanks for your informative reply.
Thank you, very much. Yes, I'm disappointed, but I'd rather know.
Having the minutia of the programmatic run-time state of the parse then
influence the parse itself, is at the heart of the perl5 phenomenon "only Perl
can parse perl", which I rather hope isn't going to be preserved in perl6.
Bootstrapping is funny that way.
Besides the tools in the environment, you've got to have at least 1GB RAM
available to build perl6. I can compile it within the Gnuroot Debian app on
my Nexus 5, which has 2GB total real ram, so it has enough even inside the
Android app. I can't similarly buil
Figuring out the environment, and how to best fit into it, is tricky, wants a
richly powerful programming language, like perl. Ideally one that's almost
certainly already available. Someday, Perl6 will be that language.
Actually, now that I think about it, I'm not as sure. Maybe, eventually, a full
perl6 compiler and runtime written entirely in perl6 might, possibly, be nice;
but using, and interoperating with, existing mature tools like e.g. make and
gcc has some big advantages, too.
I think that would be great. Also lovely if it were completely correct, which I
think is perhaps the biggest focus now, or nice and compact and fast, which
still has a way to go. Many lovely goals to enjoy working on.
I think perl6 isn't self bootstrapping, yet. Unless I've gotten myself
confused, some of the environment sniffing and basic build automation is in
perl5, and the foundation is in C. Also wants make.
Have more than 1GB RAM --- or plenty of swap, and vast patience.
Thanks, very much.
That talk inspired unhappiness in me, and I've even written my thoughts out,
but as all I've got is an unconstructive rant, I'm keeping it as an inspiration
until I can offer my own perl6 package manager that suits my prejudices.
A sample of one: if the problem is that perl6
A C char** is an array (of unknown length) of pounters to C strings ( each of
unknown length).
I don't know NativeCall, can't tell you how it should be declared, but I hope
that highlights the issue.
Thanks for the helpful note.
Perhaps I need to get to coding my own module installer. I appreciate that
"everything, everywhere, must support i18n" is noble, but I think it's pretty
ugly to encode filenames in the install tree on all systems, because there
exist systems that can't represent som
Thanks for the explanation. Sounds like an unfortunate situation, rather than
letting the system admin choose modules within the limits of filesystem
namespace, it's using a separate database, opaque to filesystem tools. I hope
this is just a temporary hack until a mature solution is hammered o
I never got panda to install, so I use zef.
The only module I've installed was Readline, to shut up the blind nagging
whenever I run perl6 for a repl.
Zef seems to have left files containing the string Readline in
share/perl6/site, plus .perl6/precomp. The filenames are hashes, perhaps from a
I think you're right, and the rpm packaging of perl5 is rather similar -- but
simpler, as there aren't the bifurcations into moarvm vs jvm, and panda vs zef.
But perl6 is young yet.
Happily, it's not too hard to package a single compiler, e.g. rakudo-moar. And
as long as you're comfy with rpmbu
Agreed. I too found panda didn't successfully install, so I just switched from
rakudo-star to rakudo, and I use zef. This package looks like it tries to build
rakudo-star, panda doesn't, it installs what bits succeed, and quietly ignores
those that don't.
I think the packager should work from r
https://www.reddit.com/r/perl6/comments/4f6jx5/building_perl6_on_android_in_gnuroot_debian/
TLDR: LDFLAGS=-Wl,-z,noexecstack And then zef install --force Readline
Moarvm wants to try to execute code off the stack, but doesn't have to. Android
blocks attempts to execute code on the stack with sel
26 matches
Mail list logo
