This might be useful... (thanks planetlisp!)
Chris Double
Wed Jun 30 17:22:09 2004
http://radio.weblogs.com/0102385/2004/07/01.html#a625
I came across a free portable arbitary precision integer and rational
arithmentic library called [1]IMath that looks useful. It is und
On 24 Jun 2004, at 21:49, Piers Cawley wrote:
Dan Sugalski wrote:
it's not exactly exciting watching two people hit return three times
in front of a roomful of people.
Although watching two people hit each other in the face with custard
pies three times in front of a roomful of people may be a lot
On Jun 30, Steve Fink said:
>On Jun-27, Jeff 'japhy' Pinyan wrote:
>
>> It creates a tree structure, not identical but similar to the array of
>> nodes Perl uses internally.
>
>Ah, good. Then I am interested. When I manage to find some time for
>hacking again, I'll graft it onto languages/regex as
On Mon, 2004-06-28 at 06:25, Dan Sugalski wrote:
> While I'm off in this "real world" thing, it'd be in our best interests to
> go do some work on parrot's standard library. A good place to start is
> with the list of functions we'll need for the upcoming pie-thon contest
Is this list compiled any
On Wed, 2004-06-30 at 07:15, Dan Sugalski wrote:
> In all those cases you've got a binary-only distribution, and a valid
> one. (In fact, one that we want to encourage) Section 4, by my reading,
> means you've got to ship source to the LGPL component.
Well, "provide source" might be a better way o
On Jun-27, Jeff 'japhy' Pinyan wrote:
> On Jun 27, Steve Fink said:
>
> >On Jun-26, Jeff 'japhy' Pinyan wrote:
> >> I am currently completing work on an extensible regex-specific parsing
> >> module, Regexp::Parser. It should appear on CPAN by early July (hopefully
> >> under my *new* CPAN ID "JA
On Wed, 2004-06-30 at 07:17, Will Coleda via RT wrote:
> This patch was applied incorrectly - the pod closer =cut ended up
> outside the C comment. (as noted by Nick Kostirya)
Yep, that was me. It's fixed and compiles now.
-- c
This patch was applied incorrectly - the pod closer =cut ended up
outside the C comment. (as noted by Nick Kostirya)
> [EMAIL PROTECTED] - Tue Jun 29 10:23:42 2004]:
>
> On Mon, 2004-06-28 at 21:30, Will Coleda wrote:
>
> > Closes the pod inside the C comment for "pmcarray"
>
> Thanks, applied.
On Tue, 29 Jun 2004, Scott Bronson wrote:
> ASSUMPTION
>
> Parrot will only link to the GMP library, right? Either static or
> shared, doesn't matter.
> 4: The Parrot project will be distributing source code, not object code,
> so this section does not apply.
Well...
The problem is distributin
Hello.
Please move =cut into C comment at classes/pmcarray.pmc file.
Nick.
Scott Bronson wrote:
On Wed, 2004-06-30 at 00:14, Ion Alexandru Morega wrote:
... there are advantages in including
the source code:
- GMP's compilation process is aware of the machine's hardware,
making optimisations accordingly. It should be compiled along with
parrot, for better perfor
On Wed, 2004-06-30 at 00:14, Ion Alexandru Morega wrote:
> ... there are advantages in including
> the source code:
> - We could trim down all the functionality we don't use (if there is
> any)
On modern architectures, I don't think that this will actually buy very
much. Shared libraries ar
I haven't read the LGPL carefully, but there is one point i'd like to make.
Scott Bronson wrote:
ASSUMPTION
Parrot will only link to the GMP library, right? Either static or
shared, doesn't matter.
It would certainly work that way, but there are advantages in including
the source code:
- We co
13 matches
Mail list logo
