# New Ticket Created by "Mr. Nobody"
# Please include the string: [perl #15904]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15904 >
lib/Parrot/Configure/Step.pm has these statements at
lines 74 and 76:
# New Ticket Created by "Mr. Nobody"
# Please include the string: [perl #15925]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15925 >
The command.com shell in windows 9x dosen't recognize
2>&1
# New Ticket Created by "Mr. Nobody"
# Please include the string: [perl #15948]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=15948 >
I sent this patch before but it got the wordwraps
messed up, its e
libparrot.a is not really related to testing, it should belong in "all". This
patch does so, and as a side effect, t/src/basic will now work with "make testj".
__
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
-
The first enclosed patch quashes "invalid pragma" warnings in platform.h, the
second one makes another exception to imcc requiring (maybe imcc
should come with a sysexits.h instead?)
__
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
ht
While Apocolypse 5 raises some good points about problems with the old regex
syntax, its new syntax is actually worse than in perl 5. Most regexes, such
as this one to match a C float
/^([+-]?)(?=\d|\.\d)\d*(\.\d*)?([Ee]([+-]?\d+))?$/
would actually become longer:
/^(<[+-]>?)\d*(\.\d*)?(<[Ee]>(
While Apocolypse 5 raises some good points about problems with the old regex
syntax, its new syntax is actually worse than in perl 5. Most regexes, such
as this one to match a C float
/^([+-]?)(?=\d|\.\d)\d*(\.\d*)?([Ee]([+-]?\d+))?$/
would actually become longer:
/^(<[+-]>?)\d*(\.\d*)?(<[Ee]>(
--- Ramesh Ananthakrishnan <[EMAIL PROTECTED]> wrote:
> Is it possible to write networking code in Parrot?
Not yet. Someday there will probably be a Sockets extension for parrot (not
really used enough to justify being in the core)
__
Yahoo! - We R
> t/pmc/nci.t doesn't like me or, at least, it doesn't like the way I
> don't have a lrint in my . My K&R claims that everything in
> math.h ought to return a double (well, anything you can validly expect
> to find in every math.h), so using math.so is probably not the way to
> test the nci, inste
There are some files in parrot that have names common in the first 8
characters. This will cause problems if someone tries to compile Parrot on
DOS. Is DOS an intended target, or should we not worry about this?
/core_ops*.c
/docs/packfile*.pod
/examples/assembly/benchmarks/gc*.pasm
/icu/source/dat
--- [EMAIL PROTECTED] wrote:
> I thought that something like what follows:
>
> goto _foo
> end
> _foo:
> print "Howdy!\n"
> end
>
> would be legal imcc input
IMCC requires you to put everything in .subs. So it should be something like
..sub main
goto _foo
end
_foo:
print "H
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> ..sub main
> ..end
Except without those extra dots. Stupid mailer.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
> This is a bit of an oversimplification. $foo and @foo do not always
> behave the same, even if $foo and @foo refer to the same array object.
> In particular, $foo doesn't behave like @foo in a list context.
> Scalars must continue to behave like scalars in list context, even
> if they're interna
> This is a bit of an oversimplification. $foo and @foo do not always
> behave the same, even if $foo and @foo refer to the same array object.
> In particular, $foo doesn't behave like @foo in a list context.
> Scalars must continue to behave like scalars in list context, even
> if they're interna
> This is a bit of an oversimplification. $foo and @foo do not always
> behave the same, even if $foo and @foo refer to the same array object.
> In particular, $foo doesn't behave like @foo in a list context.
> Scalars must continue to behave like scalars in list context, even
> if they're interna
Sent to the wrong list. Ignore, please.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--- Steve Fink <[EMAIL PROTECTED]> wrote:
> blib/lib/libparrot$(SO) : blib/lib $(O_DIRS) $(O_FILES)
> - $(LD) $(LD_SHARED) $(LD_SHARED_FLAGS) $(LDFLAGS)
> $(LD_OUT)blib/lib/libparrot$(SO) $(O_FILES) $(C_LIBS)
> + $(LD) $(LD_SHARED) $(LD_SHARED_FLAGS) $(LDFLAGS)
> $(LD_OUT)blib${slash}lib${
--- Smylers <[EMAIL PROTECTED]> wrote:
> Murat Ünalan wrote:
>
> > print "date" if $var is int( 1..31 );
>
> I don't think that the type needs to be specified here, especially if
> the variable has already been declared to be of the required type, so a
> junction should be sufficient:
>
> prin
--- Smylers <[EMAIL PROTECTED]> wrote:
> David Storrs wrote:
>
> > On Fri, Jan 03, 2003 at 10:58:49AM -0800, Mr. Nobody wrote:
> >
> > > --- Smylers <[EMAIL PROTECTED]> wrote:
> > >
> > > > junction should be suffic
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
> Arrays have methods:
>
> my int @a = (1..100);
> print @a.length; # prints "100"
> my @b = @a.grep { $_ > 50 }; # gets 51..100
.length is unneeded, since an array gives its length in numeric context, so
you can just say
--- Damian Conway <[EMAIL PROTECTED]> wrote:
> Chris Dutton wrote:
>
> > Given discussions about "hyper" operators in the past, I found this
> > rather interesting in the release notes.
> >
> > http://pike.idonex.com/download/notes/7.4.10.xml
>
> Interesting, but I still feel that vectorized op
--- Luke Palmer <[EMAIL PROTECTED]> wrote:
> > Date: Wed, 08 Jan 2003 12:14:10 +0800
> > From: Damian Conway <[EMAIL PROTECTED]>
> >
> > Can I suggest that an alternative solution might be the following:
> >
> > Suppose Perl 6 had two new very low precedence operators: ~> and <~
> > (a.
--- Damian Conway <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
>
> > I don't like either of these operators. What's wrong with
> >
> > @out = sort map {...} grep {...} @a
> >
> > ?
>
> For a start, if these functions were
--- Thom Boyer <[EMAIL PROTECTED]> wrote:
> Mr. Nobody <[EMAIL PROTECTED]> wrote:
> > --- Damian Conway <[EMAIL PROTECTED]> wrote:
> > > @a ~> grep {...} ~> map {...} ~> sort ~> @out;
> >
> > That's going to be just plain
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Nicholas Clark wrote:
>
>
> > So I'm confused. It looks like some bits of perl are incredibly sensitive
> to
> > cache alignment, or something similar.
>
>
> This reminds me on my remarks on JITed mops.pasm which variied ~50% (or
> more) dependi
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) ICU building
> *) Unicode encoding
Do we really need unicode in parrot? Seems to me like it dosen't really
accomplish much but making string operations much slower. People would still
be able to use it even if strings aren't encoded with it.
__
--- David Storrs <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 12, 2003 at 11:50:14AM +, Richard J Cox wrote:
> >
> > U+21DC "Leftwards Squiggle Arrow" and U+21DE "Rightwards Squiggle Arrow"
> would
> > seem to fit the bill rather well maybe the ascii <~ and ~> are merely
> > aliases of the tru
--- Buddha Buck <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
>
> >
> > Unicode operators in the core are a very, very, very, very, very, very,
> very,
> > very, very, very, very, very, very bad idea.
>
> We've already had this discussion. We wouldn
--- Thom Boyer <[EMAIL PROTECTED]> wrote:
> Mr. Nobody <[EMAIL PROTECTED]> says:
> > Unicode operators in the core are a very, very, very, very, very, very,
> very,
> > very, very, very, very, very, very bad idea.
>
> OK, now I think I know how _you_
--- Buddha Buck <[EMAIL PROTECTED]> wrote:
> Mr. Nobody wrote:
> > --- Buddha Buck <[EMAIL PROTECTED]> wrote:
> >
> >>Mr. Nobody wrote:
> >>
> >>
> >>>Unicode operators in the core are a very, very, very, very, very, very,
&g
--- "Joseph F. Ryan" <[EMAIL PROTECTED]> wrote:
> I'm having problems making off of the recent cvs snapshot. When
> running Configure, I get the errors/output below. Could anyone
> suggest a fix that I could try?
>
> I am running windows 2kpro, with gcc under cygwin as my compiler.
>
> Thanks,
--- [EMAIL PROTECTED] wrote:
> L2R/R2L syntax
> Argh! No! It's back and this time it means business. The dreaded
> left->right versus right->left thing came back, and this time it was
> Damian applying the electrodes to the corpse. Of course, it being
> Damian
> he was instantly f
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 9:51 AM -0800 1/14/03, Jonathan Sillito wrote:
> >Dan,
> >
> >Below are some questions about this ...
>
> And now some answers. :)
>
> > > -Original Message-
> >> From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
> >
> >[snip]
> >
> >> Objec
--- Garrett Goebel <[EMAIL PROTECTED]> wrote:
> From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
> > At 9:51 AM -0800 1/14/03, Jonathan Sillito wrote:
> > >
> > >Below are some questions about this ...
> >
> > And now some answers. :)
> >
> > >> From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
> > >
>
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
> --- Simon Cozens <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] (Dan Sugalski) writes:
> > > Ah, that's a different question. Having Unicode synonyms may well
> > be
> > > considered reasonable thing
> >
> > Sounds like the good old days of trigra
--- Brent Dax <[EMAIL PROTECTED]> wrote:
> Mr. Nobody:
> # --- Austin Hastings <[EMAIL PROTECTED]> wrote:
> # > It's very much like the good old days of trigraphs. But on the plus
> # > side, once all the losers get their fonts/xterms/editors
> # up-to-s
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
> Well, I don't know about anyone else, but *I'm* planning on making
> many, many Unicode synonyms, to make my code shorter and more readable.
>
> For example, C is too long, so I want to just make it curly-f,
> (Æ). And C is even longer, so I'm g
--- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> --- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
> > Well, I don't know about anyone else, but *I'm* planning on making
> > many, many Unicode synonyms, to make my code shorter and more readable.
> &g
--- Austin Hastings <[EMAIL PROTECTED]> wrote:
>
> --- "Mr. Nobody" <[EMAIL PROTECTED]> wrote:
> > --- Austin Hastings <[EMAIL PROTECTED]> wrote:
> > > --- Simon Cozens <[EMAIL PROTECTED]> wrote:
> > > > [EMAIL PROTECTED] (Dan
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
>
> So, to bring this thread back on track *again*, I hopefully offer this
> summary.
>
>
> 1) Damian's idea of using ~> and <~ as L2R and R2L is well-liked. Thus:
>
>@out = grep { ... } map { ... } @in; # (1) (perl5)
>
> be
--- Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 17, 2003 at 12:21:33PM -0500, Dan Sugalski wrote:
> > Sorry this one sat. I want to apply it, but the test patch looks to
>
> On Tue, Jan 14, 2003 at 04:53:25PM +, Bernhard Schmalhofer wrote:
> > For the operator 'abs' I use the func
--- Thom Boyer <[EMAIL PROTECTED]> wrote:
> Mr. Nobody [mailto:[EMAIL PROTECTED]] groused:
> >I have to wonder how many people actually like this syntax, and how many
> only
> >say they do because it's Damian Conway who proposed it.
>
> Some of us like it bec
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
>
> On Friday, January 17, 2003, at 11:00 AM, Simon Cozens wrote:
> > [EMAIL PROTECTED] (Michael Lazzaro) writes:
> >> ...the absence of the commas is what's special. If they were normal
> >> functions/subroutines/methods/whatever, you would need a
--- Sean O'Rourke <[EMAIL PROTECTED]> wrote:
> On Sat, 18 Jan 2003, Michael Lazzaro wrote:
> > So 'if' and friends are just (native) subroutines with prototypes like:
> >
> >sub if (bool $c, Code $if_block) {...};
>
> IIRC it's not that pretty, unfortunately, if you want to support this:
>
>
--- Miko O'Sullivan <[EMAIL PROTECTED]> wrote:
> SUMMARY
>
> C<$var ?= $x : $y> as a shortcut for C<$var = $var ? $x : $y>.
>
>
> DETAILS
>
> We have ||=, +=, -=, etc. These shortcuts (I'm sure there's some fancy
> linguistic term for them) save us a few keystrokes and clean up the code.
>
>
--- Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> BTW, what's about dmake?
> Has anybody tried to make Parrot with it?
DMAKE.EXE: makefile: line 12: Warning -- Macro `O' redefined after use
DMAKE.EXE: makefile: line 14: Warning -- Macro `A' redefined after use
DMAKE.EXE: Error -- Incomplet
--- Jos Visser <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Jos Visser
> # Please include the string: [perl #23159]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=23159 >
>
>
> --
--- Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> > Jonathan Worthington:
> > > LIB : fatal error LNK1181: cannot open input file "jit_cpu.obj"
> > > NMAKE : fatal error U1077: 'lib' : return code '0x49d'
> > > Stop.
>
> >
> > There *is* code in config/auto/jit.pl to disable JIT on Win32, so I'm n
48 matches
Mail list logo
