On 11/8/05, Will Coleda <[EMAIL PROTECTED]> wrote:
> Minor updates to the website.
>
here's some content for the 'Talks' section, slides from chip's
austrian perl workshop talk:
http://groups.google.com/group/perl.perl6.internals/browse_frm/thread/f1688a43617f47b7/488f23195bb0f206#488f23195bb0f206
On 11/11/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> I think it makes sense to rename the files to be .pm anyways as they're
> already more of a module then a script and will only become more so.
>
please rename them, as we discussed on #parrot. they can't be run as
standalone scripts, so the .
i removed a stray line of imcc code which accidentally converted an
op's full name back to it's short name (e.g. branch_p => branch). this
should make errors for missing ops or bad arguments easier to
understand, as the op full name, short name, and arg count is now
reported in the error message.
i've added six more tests to PGE for nested matches, (based on a perl5
bug report i saw,) as parrot revision 9973, in t/p6rules/capture.t. it
seems that
rx /((\w+)+)/
is failing on long strings, just like it does in the perl5 bug i saw
(#8685). however, parrot doesn't segfault like perl does, at
On 11/14/05, jerry gay <[EMAIL PROTECTED]> wrote:
> i've added six more tests to PGE for nested matches, (based on a perl5
> bug report i saw,) as parrot revision 9973, in t/p6rules/capture.t. it
> seems that
> rx /((\w+)+)/
> is failing on long strings, just like it d
while adding some shiny new pge tests for return context, i came
across this PIRism:
using keyed string access to the match object
##...
rulesub = p6rule('$:=(.)')
match = rulesub('abc')
.local string res
res = match['A']
print res
## prints: a
using keyed
On 11/14/05, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 14, 2005 at 06:59:51PM -0800, jerry gay wrote:
> > it seems that in keyed string access to the match object, the result
> > is returned directly as a string. in keyed integer access to the match
> &
from a read of the spec, the expected behavior of this code is unclear to me.
in the rule, i'm matching the builtin whitespace rule, creating an
alias with the same name as the named rule, and matching the builtin
rule again. this brings up a few questions:
does the alias replace the named rule o
On 11/15/05, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 15, 2005 at 10:26:05AM -0800, jerry gay wrote:
> > > I guess I should go ahead and provide methods in the match objects
> > > for the other *_keyed_int operations, if only to avoid this sort of
>
i've been thinking about ways to reorganize parrot's test files, which
are currently spread throughout the source tree. so, here's my
proposal for refactoring them, for your consideration.
all parrot core tests should live under t/. notably, this includes
imcc, and other compilers like pge and tge
On 11/19/05, Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> Sound good to me. 'imcc/t' is more confusing than helpful.
> I also suggest to do away with t/imcc/reg and move it's test perhaps
> t/reg, as no PIR specific functionality is tested.
>
> t/compilers/imcc could also be t/compilers/pir.
>
On 11/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> I've like to nominate Jerry for an entry in RESPONSIBLE_PARTIES as the
> test suite maintainer. Thanks for all your work Jerry.
>
thanks for the nomination, joshua. if approved, i'll try my best to be
responsible :)
~jerry
On 11/20/05, jerry gay <[EMAIL PROTECTED]> wrote:
> for now, i've reorganized the pge tests, moving them into the
> t/compilers/pge/ directory and subdirs, in revision 10112. smoke tests
> and bug reports are welcome for all platforms. in testing, i've come
> across th
i've checked in a subset of Perl 5.9.2's regexp tests for PGE to chew
on. for now, i modified the stolen harness to emit PIR. the harness is
currently very ugly... that won't be for long, however, as i'll
refactor it soon.
currently, only 130 of 960 tests are running, as the PIR-producing
harness
your example in the previous message made me think. what will parrot
do if a parrot sub declares the :outer subpragma, and the sub to which
it refers doesn't have a lexical pad? something like:
.sub do_add3
.const .Sub add3 = "add3"
$P1 = newclosure add3
On 11/21/05, jerry gay <[EMAIL PROTECTED]> wrote:
> i've checked in a subset of Perl 5.9.2's regexp tests for PGE to chew
> on. for now, i modified the stolen harness to emit PIR. the harness is
> currently very ugly... that won't be for long, however, as i'
the parrot directory structure is large and a bit disorganized.
let me give you some examples:
* build_tools/, util/, and tools/*/ each contain utility perl
scripts. these should be grouped together under tools/, which
already contains subdirectories
* there are multiple dirs containing C sourc
On 11/28/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> Hi Jerry,
>
> I'm just curious, I don't mean to criticize your ideas. Just, give
> some "why"s for the "should"s.
>
no worries--this isn't criticism, it's feedback.
> On 11/29/0
On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> jerry gay wrote:
>
> > +---t
> > | +---compilers
> > | | +---imcc # moved from imcc/t/
> > | | |
>
> This doesn't really work for me. imcc/t* used to test some
On 11/29/05, jerry gay <[EMAIL PROTECTED]> wrote:
> On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> > This doesn't really work for me. imcc/t* used to test some general
> > parsing features, code generation and register allocation. Therefore it
&
On 11/28/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 28, 2005 at 04:45:33PM -0800, jerry gay wrote:
> > i propose reorganizing the tree to improve clarity and cohesion.
>
> Reorganization would be good at this point, but should be undertaken
> caut
On 11/28/05, Matt Diephouse <[EMAIL PROTECTED]> wrote:
> I'd really like to see imcc/docs/ get moved to docs/imcc/ while we're
> moving things around. I know that some people consider imcc to be
> rather separate from parrot, but as a compiler writer, I see it as a
> core feature. I always seem to
On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> On Nov 29, 2005, at 1:45, jerry gay wrote:
> > the parrot directory structure is large and a bit disorganized.
> > let me give you some examples:
> > * build_tools/, util/, and tools/*/ each contain utility perl
On 11/30/05, Peter Sinnott <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 30, 2005 at 03:49:36PM -, Jonathan Worthington wrote:
> > OK, attached. If you run this as a PIR example, it works just fine. If
> > you compile it to a PBC, then you get the error.
> >
> > $ parrot breaks2.pir example.dll
>
On 11/30/05, Jonathan Worthington <[EMAIL PROTECTED]> wrote:
> "Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
> > Jonathan Worthington wrote:
> >> Hi,
> >>
> >> I seem to be touching a bug related to writing compiled code.
> >>
i can't recreate this bug (r10271).
D:\usr\local\parrot\trunk>parrot br
On 12/1/05, Matt Diephouse <[EMAIL PROTECTED]> wrote:
> After many months and lots of work, I'm happy to present you with the
> latest namespace spec draft. Comments are most welcome: to quote Chip,
> "The rest of the discussion would benefit from more eyes."
>
yay! your hard work shows... this was
it seems punie's using way too much memory. in fact, it's running out
of memory on my 512MB system, and peaks at 480MB usage during PAST
generation on my machine with 1.5GB. these are win32, using msvc, and
the command i ran was
D:\usr\local\parrot\trunk\languages\punie>..\..\parrot punie2.pir dem
On 12/3/05, Bob Rogers <[EMAIL PROTECTED]> wrote:
> So, at present, lexical subs must be emitted in preorder. Is this a
> bug, a TODO, or a conscious design decision? (I'm hoping for "bug,"
> BTW, since it's not mentioned in PDD20 . . . )
>
i've added 4 tests to t/op/lexicals.t testing this. as i
On 12/5/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> Not just the steps themselves need work, there is still some fairly
> substantial work left to be done on the configure framework as part of
> my refactoring project. This has been going rather slowly because it's
> usually bad to major radic
On 12/5/05, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
> hi,
>
> attached is a patch that adds the new ".lex" syntax. The description is
> copy/paste from PDD20.
>
thanks, applied to docs/imcc/syntax.pod as r10354.
it seems mail from RT is a little slow, so you may not have been aware
of the recent
n 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. related is moving the tools/* files to the proper
> subdirs, and renaming them where appropriate. this should be grouped
> with ot
On 12/6/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> 2) I'm very much inclined to remove the Win32 special casing (see also
> r8673)
>
> There are already 2 possibilities to specify the runtime prefix (where
> libs are searched).
> a) perl Configure --prefix=foo
> This sets the built in pre
On 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. related is moving the tools/* files to the proper
> subdirs, and renaming them where appropriate. this should be grouped
> with ot
On 12/6/05, jerry gay <[EMAIL PROTECTED]> wrote:
> On 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> i'm pretty confident all will go well, so this change should be
> committed in less than an hour. it only affects the root and languages
> makefiles, manifests
On 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. this should be grouped with other compiler/-related
> modifications.
>
it did, but they were minor ones. next is imcc/, which i expec
On 12/6/05, Michael Cummings <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-12-06 at 18:38 -0500, Michael Cummings wrote:
>
> t/perl/manifest..Can't exec "svk": No such file or
> directory at t/perl/manifest.t line 38.
> ok
> 1/3 skipped: Not a working copy
>
> Not a patch, b
On 11/29/05, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> this will likely require configure, makefile, build, and documentation
> modifications. this should be grouped with other compiler/-related
> modifications.
> Note: see the parent ticket for more information.
>
RT is
the first phase of the directory reorganization is complete. all
directory moves which do not involve the src/ directory are done. hope
this clears things up a bit. next, i'll be addressing src/ dirs. if
you'll recall from recent discussion...
On 11/29/05, jerry gay <[EMAIL PROT
On 12/8/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2005, at 18:54, jerry gay wrote:
> > chip proposed changing the src/ dir to vm/. nobody complained,
>
> I have said several times that I don't see any reasons to rename src.
>
okie-dokie, then. that
On 12/8/05, jerry gay <[EMAIL PROTECTED]> wrote:
> the first phase of the directory reorganization is complete. all
> directory moves which do not involve the src/ directory are done. hope
> this clears things up a bit. next, i'll be addressing src/ dirs. if
> you'll r
On 12/10/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> I really do believe that docs/imcc should be renamed to docs/pir and
> that all references to imcc be removed form docs/pir/*.pod.
>
> Are there any objections to this?
>
imcc is the compiler for three languages: PIR, PASM, and PAST.
therefor
On 12/8/05, jerry gay <[EMAIL PROTECTED]> wrote:
> On 12/8/05, jerry gay <[EMAIL PROTECTED]> wrote:
> > the first phase of the directory reorganization is complete. all
> > directory moves which do not involve the src/ directory are done. hope
> > this clea
On 12/12/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Here's a side by side comparison, Revision 10460, of
> Visual C++ 7.1 and 8.0.
>
great!
> arithmetics.t suffers from -0.0 vs 0.0 problems. We've had something
> similar some time ago. They seem to have changed that in 8.0, as the
> test pass
as per leo, BigInt needs tests *badly*.
BigInt also needs some design, as currently only gmp can be used to
support BigInts. but i'll leave that for another ticket.
~jerry
On 12/10/05, jerry gay <[EMAIL PROTECTED]> wrote:
> pf/ has been moved to src/packfile/, types/ to src/types/, and with a
> little cleanup from leo due to a mistake i made (sorry!), ops/ has now
> been moved to src/ops/.
>
> next on the list is io/.
>
io/ has been moved un
directory reorganization is nearly done. all directories on my list
have been moved, save one; the only remaining directory to move is
jit/. this will require some reworking of the jit configure system,
and moving jit/ will also affect every platform (potentially in
different ways (but hopefully no
> Attached patch adds a Configure test for Visual C++ compilers. For
> versions greater or equal to 14.00 (aka Visual C++ 2005)
> C<_CRT_SECURE_NO_DEPRECATE> is defined, to avoid unsafe functions
> deprecation warnings.
>
> This function or variable may be unsafe. Consider using xxx_s
> in
On 12/13/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Tuesday, December 13, 2005, 7:43:07 PM, jerry gay via RT wrote:
> > applied locally, it fails on my earlier msvc install due to a version
> > comparison error:
>
> > Determining if your C compiler is act
> applied as r10500, along with a bit to add the new files to MANIFEST.
> thanks for the patch!
>
actually, this patch failed if msvc wasn't around. it reported 'done'
instead of 'no' if msvc wasn't around, also. so, i modified the probe
a bit. you'll find the latest changes in r10504.
~jerry
On 12/13/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> jerry gay wrote:
> > classes\env.pmc(26) : warning C4273: '__p__environ' : inconsistent dll
> > linkage
> > D:\usr\local\perl\bin\perl.exe build_tools\pmc2c.pl --c
> > classes\env.pmc
>
On 12/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> In it's current form ChangeLog is little more than a pointer to NEWS.
> This is really defeating the purpose of what ChangeLog is supposed to
> contain; detailed information about changes. It is also more or less
> redundant with the functio
On 12/23/05, Peter Schwenn <[EMAIL PROTECTED]> wrote:
> Dear 6Compilers,
>
questions about the internals of parrot (including build/config
trouble) are best directed instead to the perl6 internals list, so
i've copied them on my response.
> Cygwin isn't entirely happy with Parrot (don't know about
On 12/28/05, Sastry <[EMAIL PROTECTED]> wrote:
> Hi
> I tried building parrot on Linux 2.4.20 and I get the following error
> during gmake process. I have the default perl-5.8.6 built on my
> system. Can anybody suggest me what this error is and how to overcome
> this?
>
[snip extra build error i
On 11/28/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> Oh, one other thing for the renaming game:
>
> IMC vs. PIR
> Two names enter
> One name leaves
>
> /me giggles
this is now referenced in DEPRECATED (thanks to will,) and the
remaining .imc files in the parrot tree are quickly be
On 12/30/05, Peter Schwenn <[EMAIL PROTECTED]> wrote:
> What is the most commonly used development platform (os and machine) by
> folks on this group?
>
i can't answer that. i can tell you i use i386-win32-msvc, and
sometimes i386-linux-gcc. i know some others are using
x86_64-linux-gcc, ppc-darwin
On 1/3/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Recently on IRC:
>
> < Debolaz> leo: You can see the patches I made at
>
> http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/lang/parrot/patches/
> < Debolaz> The only one that's really needed to make things compile is
> patch-ac, but
>
On 1/4/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Wed, 4 Jan 2006, Joshua Hoblitt via RT wrote:
> > I'm wondering if it's worth disabling optimizations for
> > those compilation units if nobody noticed a problem in the period
> > between the tree reorganization and the breakage
On 1/4/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> And, just to be clear, that's building with
> Configure.pl --optimize=???
> (that is, exactly what optimization flags did you use?)
>
configure.pl --optimize
(which means i used perl's optimize flags: -MD -Zi -DNDEBUG -O1)
~jerry
On 1/4/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> t/run/optionsok 2/10Can't locate object method
> "new" via package "File::Temp" at t/run/options.t line 78.
> # Looks like you planned 10 tests but only ran 2.
> # Looks like your test died just after 2.
> t/run/options
for those of you who might be updating your working copies from svn
(post r10933) and wondering why so many files are changing, i did some
svn metadata cleanup today.
~ the set svn:mime-type property should now be set appropriately based
on file extension. i paid close attention to .t, .xml, .png
On 1/6/06, Roger Browne <[EMAIL PROTECTED]> wrote:
> This PIR program:
>
>.sub 'main' :main
> print_as_integer('-4')
> print_as_integer('X-4')
> print_as_integer('--4')
>.end
>
>.sub 'print_as_integer'
> .param string s
> $I0 = s
> print $I0
> p
On 1/6/06, Anders Nor Berle <[EMAIL PROTECTED]> wrote:
> This should make the FreeBSD build support building a shared libparrot.
>
thanks, applied as r10939.
~jerry
On 1/9/06, via RT Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Joshua Hoblitt
> # Please include the string: [perl #38196]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=38196 >
>
>
> Hi Folks,
>
> I
On 1/9/06, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> As a side note, Parrot::Configure::Step is only partially tested and I'm
> rather nervous about messing with it until it has better test coverage.
>
i'll work on this now.
~jerry
On 1/12/06, Alberto Manuel Brandão Simões <[EMAIL PROTECTED]> wrote:
> I'm not implementing copy at the moment as I lack knowledge. I might
> just write the default open/while(){write}/close method for cases when
> everything else fails.
>
> BTW, it will go for File.pmc accordingly with Leo.
>
sinc
On 1/12/06, Parrot Assembler via RT <[EMAIL PROTECTED]> wrote:
> This message has been automatically generated in response to the
> creation of a parrotbug regarding:
> "[BUG] (r11026) pdb.exe build broken"
>
of course that should be r11126.
~jerry
> while running 'make world' for i386-win
On 1/13/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Below are some thoughts, syntax mainly, how it could look like.
>
> Proposal: Named Arguments
>
[snip proposal]
>
> Comments welcome,
> leo
>
it's not stated explicitly in your proposal, but what is the proper
location for named params in a s
On 1/13/06, Roger Browne <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-01-13 at 17:01 +0100, Leopold Toetsch wrote:
>
> > 885/4851 subtests failing, 81,76% okay.
>
> Wow, that's a lot of tests affected by this one thing.
>
most of them are in the PGE tests. since there are over 1,300 PGE
tests, and and
On 1/13/06, jerry gay <[EMAIL PROTECTED]> wrote:
> i'll fix PGE, which will leave only about 135 failures, many of which
> are in library code (no surprise there.) with a little help, i think
> we can squash these failures in no time.
>
on second thought... before i go
On 1/13/06, Bob Rogers <[EMAIL PROTECTED]> wrote:
> still in progress). Unless somebody would like to see a patch with just
> the test cases, both marked 'TODO'?
>
what's a 0.4.1 release without some TODO tests? the more the better.
~jerry
On 1/17/06, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> perl modules necessary for parrot configuration, development, and
> testing have been either committed to the parrot repo, assumed to be
> installed by the user, or (in some cases) checked for in code that
> uses them.
>
On 1/18/06, Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> jerry gay (via RT) schrieb:
> >perl modules necessary for parrot configuration, development, and
> >testing have been either committed to the parrot repo, assumed to be
> >installed by the user, or (in some
On 1/16/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Roger Browne wrote:
>
> > Wow, it really does work. Thanks! Although it misses the case where the
> > called sub has zero .params:
> >
> >.sub 'main' :main
> > errorson 0x0C
> > foo(5)
> >.end
> >.sub foo
> > pri
> pdd11 seems to be out of step with extend.h
>
> Patch attached.
>
thanks, applied as r11275.
~jerry
On 2/2/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 02, 2006 at 11:33:25AM +0100, Leopold Toetsch wrote:
> > On Feb 2, 2006, at 2:33, Allison Randal (via RT) wrote:
> >
> > >I've spent too much time on this error, so I'm routing around it, but
> > >I'd love to figure out what's c
On 2/6/06, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 06, 2006 at 11:23:40AM +, Roger Browne wrote:
> > Chip Salzenberg wrote:
> > > I'm struggling with good PIR syntax for it
> > > though ... Void calls will be common, so it'd be nice to express
> > > them easily.
> >
> > How abo
On 2/6/06, Allison Randal <[EMAIL PROTECTED]> wrote:
> On Feb 5, 2006, at 3:05, Leopold Toetsch via RT wrote:
> >
> > .sub "dump" method
> > .param int level
> >
> > The level argument isn't optional at all. Turning on argument count
> > checks would prevent such errors.
> > It has to be:
> >
while debugging partcl, leo asked will for some source comments to
understand where the generated code came from. i thought it should be
possible to walk the chain from the code emitter, and print the
calling sub's filename and line number in PIR.
walking the call chain is possible using a ParrotI
On 2/8/06, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> ~ the official text will be associated to each file in the parrot
> repository via a new svn keyword, 'Copyright'
now DONE, r11501.
still TODO:
> ~ copyright text in each text file will be replaced with the ne
On 2/10/06, Stig Brautaset <[EMAIL PROTECTED]> wrote:
> Stig
>
applied already in r11502.
thanks for reporting.
~jerry
On 2/10/06, jerry gay <[EMAIL PROTECTED]> wrote:
> On 2/8/06, via RT jerry gay <[EMAIL PROTECTED]> wrote:
> > ~ copyright text in each text file will be replaced with the new
> > keyword for expansion
> > ~ committers will be instructed on setting their environme
On 2/15/06, via RT Andy Dougherty <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Andy Dougherty
> # Please include the string: [perl #38577]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=38577 >
>
>
> Would there be
On 2/17/06, Matt Fowles <[EMAIL PROTECTED]> wrote:
> $ svn --version
> svn, version 1.1.4 (r13838)
>compiled May 13 2005, 06:29:47
>
> How bout you?
>
can't hurt to upgrade...
>svn --version
svn, version 1.3.0 (r17949)
compiled Jan 15 2006, 23:18:48
~jerry
previously, the get_string method of the .None PMC returned "None".
it's been modified to return the somewhat more sane "", or empty
string. this may affect code using .Hash PMCs, as the get_string
method of the .None PMC is called when the value of a non-existant
hash key is requested in string co
On 4/14/06, chromatic <[EMAIL PROTECTED]> wrote:
> Looking at patch #12967, particle revised a previous patch and replace @slash@
> with / in paths in the Makefile. I used the former out of a cargo-cult sense
> of platform independence. Is that unnecessary, or is it still a good idea?
>
config/ge
On 4/13/06, via RT Gregor N. Purdy <[EMAIL PROTECTED]> wrote:
> Determining if your C compiler is actually gcc...
> step auto::gcc died during execution: C compiler failed (see
> test.cco) at lib/Parrot/Configure/Step.pm line 362
what does test.cco say?
On 4/24/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> The patch included below changes lib/Parrot/Revision.pm and
> lib/Parrot/Distribution.pm back to 5.006, and appears to be
> the minimal change needed to get back to building with perl-5.6.x.
>
i'm of the "don't repeat yourself" camp, so as of
On 4/24/06, Larry Wall <[EMAIL PROTECTED]> wrote:
> If you want to reset to before the key for some reason, you can always
> set .pos to $.beg, or whatever the name of the method is. Hmm,
> that looks like it's unspecced.
>
BEGIN
.beg looks over-huffmanized to me. .begin is more natural to
english
On 4/22/06, Will Coleda via RT <[EMAIL PROTECTED]> wrote:
> This issue is long dead, isn't it?
>
this has been fixed some time ago, yes. however, tcl's not building
for me right now for a different reason...
link -nologo -nodefaultlib -debug -dll -out:tcl_group.dll
"lib-tcl_group.obj" "tclobject.o
On 12/22/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Tuesday, December 20, 2005, 8:09:32 PM, François PERRAD wrote:
> > At 11:53 16/12/2005 +0100, you wrote:
>
> >>I can think of two ways to fix this:
> >>
> >>- Hide every env access behind the platform stuff. That is, add
> >>something like Par
On 4/27/06, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Here's another round of test results on my box. I've also added the
> details for the tests that failed. The C and
> are not unexpected on Windows.
>
> Failed Test Stat Wstat Total Fail Failed List of Failed
> -
On 4/27/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Apr 2006, jerry gay wrote:
>
> > On 4/27/06, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> > > Here's another round of test results on my box. I've also added the
> > > details
On 4/27/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Thu, 27 Apr 2006, jerry gay wrote:
>
> > On 4/27/06, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> > > Here's another round of test results on my box. I've also added the
> > > details
bernhard++ # this seems to have been fixed
On 4/30/06, via RT jerry gay <[EMAIL PROTECTED]> wrote:
# New Ticket Created by jerry gay
# Please include the string: [perl #39035]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.h
after 13473 (bernhard++ for trying) building parrot now fails during
src/platform.c
src\platform.c
platform.c
config\gen\platform\generic\math.c(15) : error C2375: 'Parrot_signbit'
: redefinition; different linkage
include\parrot\platform_interface.h(16) : see declaration of
'Parrot_signbi
i noticed a few things missing from the list of sigils. patch inline below.
~jerry
Index: design/syn/S02.pod
===
--- design/syn/S02.pod (revision 9154)
+++ design/syn/S02.pod (working copy)
@@ -494,8 +494,8 @@
$ scalar
@
that's postfix ::, as mentioned in the Names section of S02.
There is no longer any special package hash such as %Foo::. Just
subscript the package object itself as a hash object, the key of which
is the variable name, including any sigil. The package object can be
derived from a type name by us
according to S02, under 'Literals', generalized quotes may now take
adverbs. in that section is the following comment:
[Conjectural: Ordinarily the colon is required on adverbs, but the
"quote" declarator allows you to combine any of the existing adverbial
forms above without an intervening colo
On 6/2/06, Rene Hangstrup Møller <[EMAIL PROTECTED]> wrote:
Hi
I am toying around with Parrot and the compiler tools. The documenation
of Perl 6 grammars that I have been able to find only describe rule. But
the grammars in Parrot 0.4.4 for punie and APL use rule, token and regex
elements.
Can
audreyt++ pointed out on #parrot that there doesn't seem to be a way
to specify where to start finding lexicals, in support of perl's
OUTER::. eg. (from S04):
my $x = $OUTER::x;
or
my $x = OUTER::<$x>;
i propose this should be specified using a three-arg form of find_lex
where the third
1 - 100 of 608 matches
Mail list logo
