Dave Whipp wrote:
I actually agree that your explicit definition (a simple/efficient
implementation in terms of other operators) is better for prelude than
my "declarative" form (which isn't really declarative, because Perl6
isn't a declarative language). My only disagreement was with your
ear
Darren Duncan wrote:
I don't quite follow you. Are you saying your version of sqrt is an
implicit declaration; maybe I don't understand how that differs from an
explicit definition in this case? In any event, right at this moment I
can't think of an answer to your question. Go ahead with wh
Dave Whipp wrote:
Darren Duncan wrote:
Dave Whipp wrote:
sub sqrt(Num where { 0 <= $_ <= Real::Max } $x) {
(0..$x/2 :by(Real::Epsilon)).min: { abs $x - $^candidate ** 2 }
}
So do you really mean "as declarative a manner as possible"? Or would
you consider this example to go beyond "possib
Darren Duncan wrote:
Dave Whipp wrote:
sub sqrt(Num where { 0 <= $_ <= Real::Max } $x) {
(0..$x/2 :by(Real::Epsilon)).min: { abs $x - $^candidate ** 2 }
}
So do you really mean "as declarative a manner as possible"? Or would
you consider this example to go beyond "possible"?
I would decl
Dave Whipp wrote:
I do agree that a prelude.pm should be written atas higher level as
possible, but I would not that Perl6 is not a "declarative" language.
Using the most powerful operators available (I'd like to see more of
them) is about the best you can do: as soon at you start using
codebl
Darren Duncan wrote:
1. What we *should* be doing with the Prelude, like with STD.pm, is
write under the assumption that the implementation is also written in
Perl 6.
We should write the Prelude in as declarative a manner as possible,
saying *what* we want to happen rather than how, such as
On Jan 14, 9:01 pm, pmich...@pobox.com (Patrick R. Michaud) wrote:
Sorry for the 'tldr' reply...
> Source code repository
> --
> This is the immediate issue at hand, because we need to move Rakudo
> out of the Parrot repository so that it can cleanly move to its new
> home at
The Prelude could be helpful for training. I've been trying to work out a
logical path into Perl 6 for quite some time, not least because it's been
a moving target. If there's a set of definitions that a computer can
follow, humans should be able to move along that path too.
--
Email and sh
Sorry for the 'tldr' reply...
On Jan 14, 9:01 pm, pmich...@pobox.com (Patrick R. Michaud) wrote:
> Source code repository
> --
> This is the immediate issue at hand, because we need to move Rakudo
> out of the Parrot repository so that it can cleanly move to its new
> home at p
> From: Patrick R. Michaud [mailto:pmich...@pobox.com]
> [...]
> Web site / blog / wiki
> [...]
> Currently Rakudo really does not have a dedicated website
> providing basic information about it. There is the
> http://rakudo.org/ site, but it's currently more of a
> blog than a true web site. For
On Thu, Jan 15, 2009 at 8:31 PM, Jon Lang wrote:
> Forgive my ignorance, but what is a Prelude?
>
> --
> Jonathan "Dataweaver" Lang
>
The stuff you load (and execute) to bootstrap the language into utility on
each invocation. Usually it's written in terms of the language you're
trying to bootst
Following some responses I've seen, I'll try to clarify my proposal. Basically
its like this.
A significant subset of Perl 6 native features, eg types and operators, native
meaning they are declared and described in the Perl 6 Synopsis documents, have
been implemented under Pugs by being writ
On Thu, Jan 15, 2009 at 8:59 PM, Jon Lang wrote:
> OK, then. If I'm understanding this correctly, the problem being
> raised has to do with deciding which language features to treat as
> primitives and which ones to bootstrap from those primitives. The
> difficulty is that different compilers p
On Thu, Jan 15, 2009 at 6:45 PM, Jonathan Scott Duff
wrote:
> On Thu, Jan 15, 2009 at 8:31 PM, Jon Lang wrote:
>>
>> Forgive my ignorance, but what is a Prelude?
>>
>> --
>> Jonathan "Dataweaver" Lang
>
> The stuff you load (and execute) to bootstrap the language into utility on
> each invocation
Jon Lang wrote:
Forgive my ignorance, but what is a Prelude?
The Prelude is a file written in Perl 6 that defines some Perl 6 built-ins.
See http://perlcabal.org/svn/pugs/view/src/perl6/Prelude.pm for what AFAIK is
the newest version.
-- Darren Duncan
Forgive my ignorance, but what is a Prelude?
--
Jonathan "Dataweaver" Lang
Geoffrey Broadwell wrote:
The problem with this method is that there are usually *several* ways to
implement each feature in terms of some number of other features. The
creators of the shared prelude are then stuck with the problem of
deciding which of these to use. If their choices do not matc
On Thu, 2009-01-15 at 16:03 -0800, Darren Duncan wrote:
> Patrick R. Michaud wrote (on p6c):
> > On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
> >> Another thing to keep in mind is that once we start to have a Perl 6
> >> prelude, we might decide to be nice neighbors and share it wit
Patrick R. Michaud wrote (on p6c):
On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
Another thing to keep in mind is that once we start to have a Perl 6
prelude, we might decide to be nice neighbors and share it with other
implementations, as far as that's practical.
My guess is t
- Original Message
> From: Patrick R. Michaud
> Moritz already replied with why spectest is currently in pugs, I
> tend to agree. For now I'd like spectests to continue to have
> a very liberal commitbit policy, and that may or may not be
> compatible with Rakudo's commitbit policy (de
On Wed, Jan 14, 2009 at 11:57:02PM -0800, Ovid wrote:
> > From: Patrick R. Michaud
>
> What's the rationale for the spectest suite to remain in the
> pugs repository? AFAICT, pugs is no longer being actively
> developed and I wouldn't be surprised if many of its spectests
> currently break an
On Thu, Jan 15, 2009 at 08:53:33AM +0100, Moritz Lenz wrote:
>
> Another thing to keep in mind is that once we start to have a Perl 6
> prelude, we might decide to be nice neighbors and share it with other
> implementations, as far as that's practical.
My guess is that there will be a shared pre
On Thu, Jan 15, 2009 at 04:20:28PM -, a...@ippimail.com wrote:
> As outlined, the requirements seem to be pretty much those of any major
> Open Source development project. Keeping this in mind might yield a
> generic template usable by other projects in future.
>
> Solving generic problems rat
As a comment to my use.perl journal post, Infinoid wrote:
> Earlier today on the IRC channel, Will Coleda made an
> interesting comment regarding partcl.
>
> 07:28 <@Coke> I'd rather have folks go to /partcl/ to get parrot.
>
> That makes a lot of sense. So, have you given much thought to how
>
As outlined, the requirements seem to be pretty much those of any major
Open Source development project. Keeping this in mind might yield a
generic template usable by other projects in future.
Solving generic problems rather than specific ones does involve a little
more thought, (it's possible to
Ovid (>), Patrick (>>):
>> Many people have strongly suggested that we switch to
>> using "git" as our version control system. At the moment I'm
>> neither strongly in favor of nor strongly opposed to switching
>> version control systems, but we have to recognize that at least
>> two of Rakudo's "
- Original Message
> From: Patrick R. Michaud
> Many people have strongly suggested that we switch to
> using "git" as our version control system. At the moment I'm
> neither strongly in favor of nor strongly opposed to switching
> version control systems, but we have to recognize that
Ovid wrote:
> - Original Message
>
>> From: Patrick R. Michaud
>
>> Source code repository
>> --
>> This is the immediate issue at hand, because we need to move Rakudo
>> out of the Parrot repository so that it can cleanly move to its new
>> home at parrot.org. Curr
- Original Message
> From: Patrick R. Michaud
> Source code repository
> --
> This is the immediate issue at hand, because we need to move Rakudo
> out of the Parrot repository so that it can cleanly move to its new
> home at parrot.org. Currently Rakudo Perl lives
As a Rakudo contributor I feel I should comment on this, although most
of my comments aren't all that exciting.
Patrick R. Michaud wrote:
> Source code repository
> --
[...]
> Many people have strongly suggested that we switch to
> using "git" as our version control system. At
30 matches
Mail list logo
