Larry Wall schreef:
> @@ -104,32 +115,34 @@
> =item round
>
> multi Num::round ( Num $x--> Int )
> + multi Int ( Num $x--> Int )
>
> -Returns the nearest integer to $x, away from zero. In other words,
> -the absolute value, rounded up.
> +Returns the nearest integ
Larry Wall schreef:
> +=item pi
> +
> + constant Num Num::pi = atan(1,1) * 4;
> + constant Int Int::pi = 3;
> [...]
> =item I
> [...]
> + multi Num::func ( Num $x: :$base = 'radians' --> Num )
> + multi Math::Trig::func ( Num $x = $+_, :$base = 'radians' --> Num )
>
> where I is on
On Wed, Feb 08, 2006 at 08:49:54PM +0100, Leopold Toetsch wrote:
> I'm still having troubles, when thinking about namespace PMCs and
> implementation thereof. Especially the relationship of class namespaces
> and the store_global opcode.
As well you might. :-, There's a chicken/egg problem in t
On Mon, Dec 05, 2005 at 04:41:21PM +0100, Leopold Toetsch wrote:
> On Dec 5, 2005, at 5:55, Matt Diephouse wrote:
> >>- perl5: sometimes (via sigil, but $ref_tosub)
> >>- perl6: maybe (sigil is part of the symbol name, but $ref)
> >
> >Functions, variables, and namespaces _are_ separate here. Don'
On Fri, Feb 24, 2006 at 12:57:24AM +0100, Leopold Toetsch wrote:
> On Feb 24, 2006, at 0:23, Patrick R. Michaud wrote:
> >>[...]
> >I've just committed an update (r11722) that eliminates PGE's
> >use of save/restore opcodes in the code it generates -- indeed,
> >PGE no longer has any save or restor
On Mon, 27 Feb 2006, Allison Randal via RT wrote:
> > It looks like 'node.set_node' doesn't actually end up doing
> > anything.
>
> Andy, could you try this again on the 0.4.2 release of Parrot? I cleaned
> up the method declaration syntax just before the release. It might help.
I haven't done a
# New Ticket Created by Allison Randal
# Please include the string: [perl #38647]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38647 >
The attached suggested patch standardizes the format of the completed
PDDs to what'
Hi all,
I'm not proposing to write a Test::SQL module, but I am tired of having
the following two things not being equivalent:
CREATE TABLE foo (
id INTEGER NOT NULL PRIMARY KEY,
name VARCHAR(32) NOT NULL,
title
age INTEGER
);
And:
create table foo (
id
On Sunday 26 February 2006 20:48, Beau E. Cox wrote:
> Hi -
>
> My Sunday svn download / make of parrot and pugs
> failed today; parrot revision 11753 built fine, but
> pugs revision 9188 failed in make smoke and
> make install:
>
> ...
> Skipping Pugs.Run ( src/Pugs/Run.hs, dist/build/Pug
The Simple Life of Muhammad (SAWS)
If we compare the life of Muhammad (Sallalhu alaihi wa sallam - SAWS) before
his mission as a prophet and his life after he began his mission as a prophet,
we will conclude that i
Ovid wrote:
> Hi all,
>
> I'm not proposing to write a Test::SQL module, but I am tired of having
> the following two things not being equivalent:
>
> CREATE TABLE foo (
> id INTEGER NOT NULL PRIMARY KEY,
> name VARCHAR(32) NOT NULL,
> title
> age INTEGER
> );
>
On Monday 27 February 2006 16:35, Beau E. Cox wrote:
> Is it me or thee? Any ideas out there?
I'm seeing the same thing on Linux PPC.
-- c
I'm helping plan inmprovements to a build & deploy system and am
wondering what people think is the "best practice" for handling
version control of locally-installed CPAN modules.
We have a bunch of code in version control (CVS now, moving to SVN soon)
We also have a large number of CPAN module
Hello Matisse,
I like these two ideas:
Matisse Enzer <[EMAIL PROTECTED]> wrote:
> 2) Put the CPAN .tar.gz files in a local CPAN repository and use
> CPAN::Site to install - that way we *only* get the versions in
> our local CPAN repository and dependencies are managed by the
>
On Mon, 27 Feb 2006, Matisse Enzer wrote:
> I'm helping plan inmprovements to a build & deploy system and am
> wondering what people think is the "best practice" for handling
> version control of locally-installed CPAN modules.
> 3) Put the .tar.gz files in our source-code control system, and
On Feb 27, 2006, at 8:14 PM, Dr Bean wrote:
There is some interesting advice in the subversion book.
Linkname: Vendor branches
URL:
http://svnbook.red-bean.com/nightly/en/
svn.advanced.vendorbr.html#svn.advanced.vendorbr.general
Thanks - that looks interesting, although complica
ess can take of resolving
dependencies. The downside is having yet-another-repository.
Whatever we do we would like to have a single-step build and release
process:
./build_script.pl --build-number=20060227-001 --environment=QA
and that will deploy both our code AND the CPAN modules we us
17 matches
Mail list logo
