See Moritz Lenz' response to this thread on March 26. To summarize, you can use
"trusts". Also having to do this may indicate bad code design. -- Darren Duncan
On 2015-05-11 2:13 PM, R. Ransbottom wrote:
I need to test some private routines, so is there a way to do tha
On 2015-05-12 12:40 PM, R. Ransbottom wrote:
On Mon, May 11, 2015 at 03:22:46PM -0700, Darren Duncan wrote:
you can use "trusts". Also having to do this may indicate bad code
design. -- Darren Duncan
I saw Moritz' and Carl's responses and I agree with the smell
issue.
Also, there are other newer API docs than the Synopsis that are useful for
study, but printing all this stuff seems very excessive, even more so because
the Synopsis etc keep changing. I advise against printing this stuff in bulk.
-- Darren Duncan
On 2015-05-15 7:54 AM, Elizabeth Mattijsen
' that
isn't any less restrictive:
use Dog:auth:ver(v1.2.1..v1.2.3);
use Dog:auth:ver(v14.3..v16.2);
That is, the cross-product answer is not restrictive enough.
I don't know if this hypothetical use case has been discussed before, but if
not, I hope that the Perl 6 specifi
:auth etc. Note that I
raised this question on #perl6 myself shortly before writing perl6-language, but
the email version is better organized. -- Darren Duncan
On 2015-06-10 11:38 PM, Tobias Leich wrote:
Hi, that is a very interesting use case, and IMO a very valid one.
Currently the
I was going to say that too, about the camel trademark issues, so can you make a
version using an onion instead of a camel? See http://www.perlfoundation.org
for what I refer to. -- Darren Duncan
On 2015-06-10 11:34 PM, Moritz Lenz wrote:
Hi,
On 06/10/2015 02:01 PM, Lin Yo-an wrote:
Hi
Or a pumpkin for that matter, since Perl 5 is Pumpkin Perl. -- Darren Duncan
On 2015-06-11 7:42 PM, Darren Duncan wrote:
I was going to say that too, about the camel trademark issues, so can you make a
version using an onion instead of a camel? See http://www.perlfoundation.org
for what I
, be part of core. Exact rationals are not particularly
complicated. Its perfectly reasonable to expect in the core that if someone
does math that is known to deal with irrationals in general, that loss of
precision then is acceptable.
-- Darren Duncan
ose classes. They share the same method spaces.
Hey, that sounds like a nice elegant design, I learned something new. -- Darren
Duncan
fault. -- Darren Duncan
On 2015-10-13 1:52 AM, Richard Hainsworth wrote:
Following on the :D not :D thread, something odd stuck out.
On 10/13/2015 03:17 PM, Moritz Lenz wrote:
But hopefully none of them breaking backwards compatibility on such a large
scale. The last few backwards incompa
quot; etc will get the current behavior with
:D not being default.
I say, save any further major breaking changes before this Christmas for things
that would be really hard to change later and are sure to be worthwhile now, and
the :D thing is not one of those.
What do you think?
-- Darren
as release.
I mean, this situation seemed to be a solid example of why Perl 6's versioning
scheme exists in the first place, to deal elegantly with things like this.
-- Darren Duncan
; but they
silently actually expect Perl 6.0.0.0 semantics. We're always going to be
stuck with this problem if we don't make declarations mandatory now. That's a
much more important change to ingrain into those several hundred existing
modules, if they aren't already, nevermind the :D thing. -- Darren Duncan
Since all you want is a constant, try declaring a submethod that has no
arguments and returns the value, instead, its the same thing. -- Darren Duncan
On 2015-12-17 6:46 PM, TS xx wrote:
Hello dear perl6 users,
I was in the need of declaring a member variable as a constant integer. After
many
On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
integers? Will 6.0.0 be the first such one? -- Darren Duncan
On 2015-12-29 12:51 AM, Tobias Leich wrote:
Hi, the first official Perl 6 (the language) release is not called 6.0.0, it is
called 6.c.
And this is what has
to indicate a fork
of the spec or such, though in hindsight of your implementations leading spec
comment, I assume this is also how one indicates dependencies on a spec-leading
compiler.
Thank you.
-- Darren Duncan
On 2015-12-29 5:46 AM, Patrick R. Michaud wrote:
On Tue, Dec 29, 2015 at 01
d Ruby and
Python and Java after. I don't know yet if there is value to targeting Perl 6
at large when I have NQP; I could, but NQP is more important to do in practice I
think.
-- Darren Duncan
Considering that a non-fat Rat has a 64-bit denominator, I would expect
conversions from Num to make use of that full precision by default, and not
round off to 6 decimal places. -- Darren Duncan
Red Hat is quite conservative. Usually what happens in situations like this
when you want more up to date stuff you get it from alternate repositories that
make Red Hat compatible packages. See also repositories for Fedora or Cent OS.
-- Darren Duncan
On 2016-01-10 11:16 PM, ToddAndMargo
I very much agree with this idea, of arguing Perl 6 as a teaching language.
Academia are the ones that would appreciate what Perl 6 offers the most in the
short term, whereas industry would demand a higher standard for it becoming
popular. And the first can lead to the second. -- Darren Duncan
g
it are also doing significant rewrites to take better advantage of the new Perl
6 features and idioms that a more mechanical automatic translation wouldn't.
Did that tell you anything useful?
-- Darren Duncan
whether there is truly a good reason for the code
to work that way, or if there isn't. Keep in mind that the standard libraries
are right now some of the primary examples Perl 6 developers would have to look
at on how to write Perl 6 code. -- Darren Duncan
a. There is also precedent for a REPL to print a
similar statement like "for help type this". -- Darren Duncan
s Greek letters when you
mean symbols.
For example, ∆ is U+2206 named INCREMENT.
Is that not better, or is an actual Greek letter desired in the above example?
-- Darren Duncan
vely limit the types?
Thank you.
-- Darren Duncan
Thank you for this Timo, and to everyone else who replied. It did indeed
address what I wanted to know. -- Darren Duncan
On 2016-09-13 5:15 AM, Timo Paulssen wrote:
I'll answer based on the data structures MoarVM uses internally:
On 09/13/2016 05:13 AM, Darren Duncan wrote:> (Pre
So what are the thoughts on this? Can we get appropriate improvements into Perl
6d and implementations etc? Also, is any of what I said actually already done?
Certainly some key parts at least are not.
Thank you.
-- Darren Duncan
this email thread is
relevant to this thing that I'm working on, a DBI for Perl 6 with a PSGI/Plack
inspired design, meaning a no-mandatory-shared-code database interface:
https://github.com/muldis/Muldis-DBI-Duck-Coupling-Perl6/blob/master/lib/Muldis/DBI/Duck_Coupling/API.pod
-- Darren Duncan
And here I thought IEEE floats had distinct values to represent overflows and
underflows that were distinct from both the zeros and the infinities. -- Darren
Duncan
On 2016-11-22 8:19 PM, Zefram wrote:
Zoffix Znet via RT wrote:
The reason we have a negative floating point zero at all is more
I want to give my strong support for this proposal. Call them "curly" quotes.
The term "smart" is BAD in this context. Just like how short cars are not
"smart" even if people say that, only self-driving cars deserve that name. --
Darren Duncan
On 2016-12-04 10
On 2016-10-30 4:11 PM, Darren Duncan wrote:
On 2016-10-30 5:45 AM, yary wrote:
Before/AfterEverything are also easy to understand, and would be as natural to
use for sorting strings, eg. for saying if a database NULL should go before the
empty string or after everything else. On the other hand
yword but it may
have been something like "SUB" or "SELF". -- Darren Duncan
On 2017-02-04 12:34 AM, ToddAndMargo wrote:
Hi All,
Just out of curiosity, in Perl 6 can a subroutine call itself?
-T
I am fighting with a broken Net:FTP::rmdir in Perl 5 that
will not recuse
601 - 632 of 632 matches
Mail list logo
