On 01/11/2017 06:43 PM, yary wrote:
You don't need JIT! It's an
implementation detail that doesn't affect functionality. In
theory it improves speed at which Perl6 code runs. In
practice, it won't make a bit of difference with FTP
Hi All,
Is there a perl 6 equivalent of perl 5's "use warnings"?
Many thanks,
-T
There is a :<&&> which might be where some confusion comes from. I
guess that's there for meta operators. For example:
multi sub infix:<&&>("foo","bar") { "win" };
say "foo" && "bar" # bar
say Z&& # win
so it does kinda work actually just not as you might expect.
LL
On Thu, Jan 12, 2017 at
Hi All,
Please forgive me being a mooch here. Would some kind person please
write me a simple Windows perl 6 script so that I can see the headers?
A simple write "hello" to the screen will suffice.
Many thanks,
-T
--
~~
Computers are like air
say "hello world";
or on the command line:
perl6 -e 'say "hello world"'
There are no headers :)
LL
On Thu, Jan 12, 2017 at 2:28 PM ToddAndMargo wrote:
Hi All,
Please forgive me being a mooch here. Would some kind person please
write me a simple Windows perl 6 script
Nope. Perl6 warns you without asking for it.
LL
On Thu, Jan 12, 2017 at 2:43 PM ToddAndMargo wrote:
Hi All,
Is there a perl 6 equivalent of perl 5's "use warnings"?
Many thanks,
-T
The module installers I know of are:
https://github.com/ugexe/zef
https://github.com/tadzik/panda
They should be able to do what you need :)
On Thu, Jan 12, 2017 at 1:50 PM ToddAndMargo wrote:
> Hi All,
>
> In Windows, other than writing for it and having it crash, how
Instead of enabling warnings, you disable them on a case by case basis with
"quietly" e.g. perl6 -e 'my $foo; quietly say "is $foo"'. Likewise,
"strict" is the default.
On Thu, Jan 12, 2017 at 12:12 AM, Lloyd Fournier
wrote:
> Nope. Perl6 warns you without asking for it.
Hi,
>From https://docs.perl6.org/language/5to6-nutshell#warnings
"Warnings are now on by default.
no warnings is currently NYI, but putting things in a quietly {} block will
silence."
On 2017-01-12 03:42:22 GMT, ToddAndMargo wrote:
> Hi All,
>
> Is there a perl 6 equivalent of perl 5's
You don't need JIT! It's an implementation detail that doesn't affect
functionality. In theory it improves speed at which Perl6 code runs. In
practice, it won't make a bit of difference with FTP client/server programs.
Hi All,
In Windows, other than writing for it and having it crash, how
do I tell if I have a module installed?
I want this one, among others:
https://github.com/araraloren/Net-FTP
If I don't have the module, how do I install it?
Many thanks,
-T
--
~~
Ah. If that's the case I have nothing useful to contribute :|
LL
On Thu, Jan 12, 2017 at 4:15 PM Brandon Allbery wrote:
>
> On Thu, Jan 12, 2017 at 12:11 AM, Lloyd Fournier
> wrote:
>
> say "hello world";
> or on the command line:
> perl6 -e 'say
Hi All,
I was looking for downloading Perl 6 for windows from
http://rakudo.org/downloads/star/
rakudo-star-2016.11-x86_64 (JIT).msi
rakudo-star-2016.01-x86 (no JIT).msi
Supposedly JIT is "Runtime optimization of hot code paths
during execution"
Don't have a clue what that is. The code
On Thu, Jan 12, 2017 at 12:11 AM, Lloyd Fournier
wrote:
> say "hello world";
> or on the command line:
> perl6 -e 'say "hello world"'
>
> There are no headers :)
>
I parsed that request as asking how to write a GUI program, fwiw.
--
brandon s allbery kf8nh
This request actually was something I wanted a lot, but since
experimenting with GTK::Simple, something seemed possible.
Hence the Inform (actually Informative) module.
It's in the modules ecosystem and installs with Panda. (Panda install
Inform)
To get a popup dialog box inside a Perl 6
On Wed, 11 Jan 2017 03:03:29 -0800, sml...@gmail.com wrote:
> Okay, I get it, I shouldn't have tried to be cute in how I phrased
> that.
Right, it's a bit weird to base your argument on a fictional survey with
results you made up :)
> But do you really think I'm wrong in considering each of the
On Thu, 29 Dec 2016 13:49:40 -0800, sml...@gmail.com wrote:
> So maybe this is more of a performance bug/oversight than an RFC?
> I think all cases should give the same result that they do now.
> They just should do it in O(1) instead of O(n).
It's a bit more involved than that due to floating
# New Ticket Created by Samantha McVey
# Please include the string: [perl #130542]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130542 >
Fudged test in S02-literals/char-by-name.t
is "\c[BELL]", "", '\c[BELL] returns ,
On Tue, 10 Jan 2017 17:59:05 -0800, c...@zoffix.com wrote:
> On Tue, 10 Jan 2017 16:23:18 -0800, fernandocor...@gmail.com wrote:
> > If I write another || operator it will continue to use the original
> > version.
> >
> > https://irclog.perlgeek.de/perl6/2017-01-10#i_13895823
> >
> "So is a weird, chunked, unpredictable, and at-times absolutely wrong result
> better than correct but slow range, that at large enough values can be made
> to be non-increasing, infinite, and one that hangs when you attempt to fully
> reify it?"
"I'm sorry, Dave, I can't do that". In some
20 matches
Mail list logo