Re: Parrot with llvm-gcc 4.2

Since llvm-gcc uses the gcc front end this isn't surprising. In fact, if parrot failed to build with that compiler it would only tell us that there is something wrong with their intergration work. IMHO it would be more interesting to test with clang which might actually pick up some sort of porta

Re: Parrot with llvm-gcc 4.2

On Fri, Aug 01, 2008 at 12:47:28AM +0200, Moritz Lenz wrote: > Joshua Hoblitt wrote: > > Since llvm-gcc uses the gcc front end this isn't surprising. > > Considering that perl 5 doesn't work with XS modules when compiled with > llvm-gcc, I think it's at least w

Re: [perl #37934] [TODO] build - log file

On Fri, Feb 06, 2009 at 06:35:05PM -0800, James Keenan via RT wrote: > On Fri Jan 11 13:17:38 2008, jhobl...@ifa.hawaii.edu wrote: > > A log would be useful if it contained sufficient information to figure > > out why a test passed or failed. Similar to autoconf's config.log (an > > invaluable deb

Re: [perl #38124] [TODO] build - header file detection w/o perl5

On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT wrote: > On Sun Jan 01 19:09:51 2006, jhobl...@ifa.hawaii.edu wrote: > > auto::headers uses the Config module to detect installed header files. > > It's ok to get default values and the arch name from Config but it's not > > OK to depend

Re: [perl #37933] [TODO] build - tracing cleanup

On Fri, Feb 06, 2009 at 06:37:41PM -0800, James Keenan via RT wrote: > On Wed Dec 14 02:04:12 2005, jhobl...@ifa.hawaii.edu wrote: > > - The debugging traces could be neater > > > > Are you talking about the Parrot debugger? gdb backtraces? The w/ glibc stack backtracing that I implimented a co

silly test error

While running 'make test' on parrot-HEAD... t/src/manifest..NOK 4# Failed test (t/src/manifest.t at line 38) # Missing files in Manifest: # languages/brainfuck/README # languages/brainfuck/brainfuck.pasm # languages/brainfuck/countdown.bf # languages/brainfuck/hello

Re: silly test error

> Please remove the directory. (Or better run always update -dP in the > first place). Pulling direct from CVS got rid of 'bf'. t/src/manifest..NOK 4# Failed test (t/src/manifest.t at line 38) # Missing files in Manifest: # languages/jako/lib/Jako/Construct/Statement/Bitwise.pm # L

Re: [perl #19189] t/pmc/perlhash fails with gcc-2.95.4 or gcc-2.8.1 on SPARC

On Mon, 16 Dec 2002, Andy Dougherty wrote: > # New Ticket Created by Andy Dougherty > # Please include the string: [perl #19189] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt2/Ticket/Display.html?id=19189 > > > > On a Debian/SPARC system with gc

Re: tinderbox all in flames

> Slightly related, I think we could use some more tinderbox testers. > Someone was running the tests on Compaq's test drive boxes, but that > seems to have stopped? I've restarted my Sparc/Solaris 8 tinderbox. Defining a list of needed test platforms might be a good idea. I have plenty of old

Re: tinderbox all in flames

The scripts were written by Zach Lipton <[EMAIL PROTECTED]> and I believe he is still maintaining things. -J -- On Tue, 11 Mar 2003, Josh Wilmes wrote: > > I'm not sure who owns the TD scripts, but I'd be willing to try to get > them working again if someone could point me at them (and how to

Re: Parrot for windows?

On Fri, 14 Mar 2003, Dan Sugalski wrote: > At 6:59 PM -0800 3/13/03, Robert Spier wrote: > > > If we can't find anothr home for it, I can make a spot on > >> ftp.sidhe.org for it. Not a *fast* home, since it's either 128k or > >> 192k upstream (depending on which interface is active, don't ask)

Re: [perl #39860] [TODO] build - Configure.pl should accept --libdir, etc.

On Tue, Jul 18, 2006 at 02:09:26AM -0700, Joshua Hoblitt wrote: > # New Ticket Created by Joshua Hoblitt > # Please include the string: [perl #39860] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=39860 >

Re: Review of current stm branch code

On Thu, Aug 10, 2006 at 07:19:21PM -0700, Chip Salzenberg wrote: > * enum trailing commas are not standard > >C89 doesn't allow enum lists to end with a comma. PITA, I know, but we >can't require C99 yet. So e.g. 'thread_state_enum' needs a comma removed. Nor does C++ understand the tr

Re: Review of current stm branch code

On Thu, Aug 10, 2006 at 07:19:21PM -0700, Chip Salzenberg wrote: > * useless curlies > > -if (PMC_IS_NULL(type_hash)) > +if (PMC_IS_NULL(type_hash)) { > return core_type; > +} > hash = PMC_struct_val(type_hash); > -if (!hash->entries) > +

Re: End the Hollerith Tyranny? (linelength.t)

On Mon, Aug 21, 2006 at 07:28:14PM +0200, Leopold Toetsch wrote: > Am Montag, 21. August 2006 17:45 schrieb Chip Salzenberg: > > Well, that's fair. ?Many of us are old enough to have used such limited > > hardware, but it's all surely been relegated to the trashheap by now. ?So: > > Would anyone be

Re: [svn:parrot-pdd] r14308 - in trunk: . cage docs docs/art docs/dev docs/imcc docs/pdds docs/pdds/clip docs/stm languages languages/tcl/docs lib/Pod/Simple t/distro

I hope you didn't do that by hand. I wrote a utility last Dec. specifically for formatting Parrot's Pod. http://search.cpan.org/~jhoblitt/Pod-Tidy-0.09/ -J -- pgpzBpjkdkKah.pgp Description: PGP signature

Re: [perl #40225] Making Makefiles...

On Wed, Aug 23, 2006 at 02:24:45PM -0400, Will Coleda wrote: > > To sum up: for now, I'm working on being able to support: > > $(addprefix runtime/builtin,$(notdir $(wildcard languages/tcl/ > runtime/builtin/*.pir))) > > Which looks like gmake, but will be expanded at config time: once we >

Re: [perl #40253] [PATCH] always cast printf("%p") to (void *)

What compiler is generating warnings? -J -- On Tue, Aug 29, 2006 at 07:03:44PM -0700, Will Coleda wrote: > # New Ticket Created by Will Coleda > # Please include the string: [perl #40253] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/

Re: [perl #40253] [PATCH] always cast printf("%p") to (void *)

hich is still too many warnings, but leo noted this particular one > could stand to be fixed, as time permits.) > > On Aug 31, 2006, at 5:34 AM, Joshua Hoblitt wrote: > > >What compiler is generating warnings? > > > >-J > > > >-- > >On Tue, Aug 29, 20

Re: PDD 22 - I/O release candidate 1

On Tue, Sep 26, 2006 at 04:44:53PM -0700, Allison Randal wrote: > One piece that is currently missing is a discussion of which lightweight > concurrency model we're going to use for the asynchronous operations. > I've had ongoing back-channel conversations with various people, but I > need to co

Re: socket related constants

On Thu, Sep 28, 2006 at 09:36:13AM +0100, Nicholas Clark wrote: > > However, step 2 is easier for Perl because we're not trying to do portable > bytecode. Some constants, (such as *most* of the socket constants, but I think > not all) are defined in RFCs, so can be baked into bytecode at compile t

Re: [perl #40803] [BUG] 'make' fails on Darwin at -lgmp

I believe that the attachment containing your make output was truncated. Can you try again or just inline the make error(s)? Thanks, -J -- On Fri, Nov 10, 2006 at 06:10:42PM -0800, James Keenan wrote: > # New Ticket Created by James Keenan > # Please include the string: [perl #40803] > # in t

Re: Limiting Exported Symbols on GCC

On Thu, Apr 12, 2007 at 04:56:15PM +0200, [EMAIL PROTECTED] wrote: > On Thu, Apr 12, 2007 at 09:13:14AM -0500, Steve Peters wrote: > > On Thu, Apr 12, 2007 at 01:37:24PM +0200, Ron Blaschke wrote: > > > While poking the GCC documentation I found that there's a feature > > > available to limit the

Re: Is Parrot 1.0 too late?

On Wed, Apr 25, 2007 at 06:20:55PM +0100, Jonathan Worthington wrote: > Allison Randal wrote: > >Nicholas Clark wrote: > >> > >>I guess that the most obvious current thing that ties Parrot to the Perl > >>community is that Parrot requires a copy of Perl to bootstrap, and > >>all the > >>build tool

Re: Thank you so much Josh Hoblitt for the backtracing

I've just commit some notes on this into docs/debug.pod along with some instructions for getting a backtrace with gdb. It's worth noting that assert() calls abort() while PARROT_ASSERT currently does not so this change is not really semantically equivalent. Some people _will want_ a core file as t

Re: Floating point comparisons

A couple of comments on dealing with floats. - Use FLT_EPSILON/DBL_EPSILON from float.h - You method is total overkill, return (fabs(x - y) < DBL_EPSILON ? 1 : 0); should be sufficent (note: check with a numerical expert). - What about NANs and INFs? I typical test for one of the values being

Re: Floating point comparisons

Another issue to consider... http://www.cygnus-software.com/papers/comparingfloats/Comparing%20floating%20point%20numbers.htm#_Toc135149458 -J -- On Tue, Jul 31, 2007 at 08:46:41AM -1000, Joshua Hoblitt wrote: > A couple of comments on dealing with floats. > > - Use FLT_EPSILON/DB

Re: Floating point comparisons

I'm not sure if 0.0 == -0.0 is true on all platforms. It should be for IEEE754 compliance but in the real world... It might be nice to throw in a few tests to see if the example code below would have the same results on all platforms. -- #include #include int main () { printf("0.0 : %f\n"

should Parrot_confess() call abort()? was Re: Thank you so much Josh Hoblitt for the backtracing

t;, file, line, cond); Parrot_print_backtrace(); -exit(EXIT_FAILURE); +abort(); } -J -- On Mon, Jul 30, 2007 at 12:29:39PM -1000, Joshua Hoblitt wrote: > I've just commit some notes on this into docs/debug.pod along with some > instructions for getting a backtrace with g

Re: Quality improvement in volunteer software projects

Oops, please ignore the accidental CCs. -J -- On Thu, Aug 02, 2007 at 01:35:51PM -1000, Joshua Hoblitt wrote: > This is Martin Michlmayr Ph.d thesis: > > http://www.cyrius.com/publications/michlmayr-phd.pdf > > > -J > > -- pgpJp028CUfTB.pgp Description: PGP signature

Quality improvement in volunteer software projects

This is Martin Michlmayr Ph.d thesis: http://www.cyrius.com/publications/michlmayr-phd.pdf -J -- pgpDkJ6DbQXxe.pgp Description: PGP signature

Re: [perl #44353] [BUG] Configure.pl: verbose-step option not working with named step

The issue is here is that there is nothing in Configure.pl's output to correlate the package name of the step with the output seen from a typical run. For example, say the test that outputs "Determining architecture, OS and JIT capability..." is failing for some reason so you w

Re: should Parrot_confess() call abort()? was Re: Thank you so much Josh Hoblitt for the backtracing

Sold. commited as r20532. -J -- On Sat, Aug 04, 2007 at 12:57:25PM -0700, chromatic wrote: > On Thursday 02 August 2007 16:39:07 Joshua Hoblitt wrote: > > > Does anyone object to this patch? > > >

Re: [Win32] There's a new compiler in town (sort of)

Hi Ron, Can you submit a patch for the PLATFORMS file? -J -- On Tue, Aug 07, 2007 at 07:05:18PM +0200, Ron Blaschke wrote: > jerry gay wrote: > > On 8/7/07, Ron Blaschke <[EMAIL PROTECTED]> wrote: > >> Microsoft is working on the next iteration of their compiler, Visual C++ > >> 9.0, currently

Re: [perl #44499] Move cstrings to String Structure

On Wed, Aug 08, 2007 at 12:17:17AM -0700, chromatic wrote: > The string_from_cstring() function has a slight flaw, in that it has to > allocate a piece of memory and create a C-style string from a nice happy > STRING. It's the responsibility of the caller to discard the C string > appropriately

Re: [perl #44607] [CAGE] Hoist slurp_file() into Parrot::Util

Why not just pull Slurp or File::Slurp into the tree? Yes, writing a slurp function is trivial but (bare with me here) if it's non-trivial enough to be factored out into a module then it should be non-trivial enough to not re-invent the wheel. -J -- On Mon, Aug 13, 2007 at 07:38:36AM -0700, Andy

Re: [perl #44607] [CAGE] Hoist slurp_file() into Parrot::Util

On Tue, Aug 14, 2007 at 07:11:36AM -0700, jerry gay wrote: > i started Bundle::Parrot to work towards the goal of removing all > external modules from the parrot repository. external modules don't > belong in the repository unless we need to fork them from their CPAN > version. unfortunately, this

Re: Tinderboxens

> What happend to the tinderboxens? ATM only two are running: > galactic-tcc and adrastea. I restarted the scripts on aniani. I'm at a loss as to why they stopped running. -J --

Re: Tinderboxens

> This might be a time to do a Tinderbox v2 rev. The current tinder > model works pretty well, but it's got some error identification > issues, and since it works in a "fetch, build, test, sleep, repeat" > mode if something goes horribly wrong the box stops. A cron-style > periodic fire-off job mig

Re: Tinderboxens

I haven't heard back from Zach on this yet but I think that a separate list for 'tinderbox' would be appropriate. Discussion of the rewrite probably doesn't need to be on p6i. My favored names would be tinderbox@ or [EMAIL PROTECTED] Suggestions? -J --

Re: Current PLATFORMS

Parrot 0.1.0 builds on Linux/x86_64 w/gcc 3.3.3 (20040217) and glibc-2.3.3 (pre20040207) but a number of tests fail. I can provide the complete test run if anyone thinks it will be helpful. -J -- Failed TestStat Wstat Total Fail Failed List of Failed -

Re: Current PLATFORMS

On Tue, 2 Mar 2004, Leopold Toetsch wrote: > x86_64 is nowadays amd64 I presume. Can you please provide the output of > $ cat myconfig AMD originally was calling it x86-64. So it went into the Linux kernel as ./arch/x86_64. Then AMD renamed the instruction set to AMD64. Just to keep it confu

Re: Current PLATFORMS

On Tue, 2 Mar 2004, Leopold Toetsch wrote: > x86_64 is nowadays amd64 I presume. Can you please provide the output of > $ cat myconfig Summary of my parrot 0.1.0 configuration: configdate='Tue Mar 2 11:51:06 2004' Platform: osname=linux, archname=x86_64-linux jitcapable=0, jitarchnam

Re: Dates and Times

On Wed, 3 Mar 2004, Dan Sugalski wrote: > FWIW, if we start getting into the "What should our base time for the > epoch be" arguments, I'll warn you that the answer if I have to make > one is probably Nov 17, 1858 at midnight, give or take a bad memory, > and our time value'll be a 64-bit integer.

Re: Dates and Times

On Wed, 3 Mar 2004, Larry Wall wrote: > Well, you can do whatever you like with Parrot, but I want Perl 6's > standard interface to be floating point seconds since 2000. Floating > point will almost always have enough precision for the task at hand, > and by the time it doesn't, it will. :-) Ar

Re: Dates and Times

On Wed, 3 Mar 2004, Dan Sugalski wrote: > At 12:59 PM -0800 3/3/04, Larry Wall wrote: > >On Wed, Mar 03, 2004 at 10:21:37AM -1000, Joshua Hoblitt wrote: > >: On Wed, 3 Mar 2004, Larry Wall wrote: > >: Anyways, I recall some discussion on p6l from years ago about using

Re: Dates and Times

On Wed, 3 Mar 2004, Dan Sugalski wrote: > Gah. OK, I'm about to declare that the time op *always* returns time > as GMT, though without specifying an epoch, unless someone's got a > good reason not to. That takes at least one variable out of the > problem. The GMT system is dead... do you mean UT

Re: Dates and Times

On Wed, 3 Mar 2004, Zellyn Hunter wrote: > For those of you not up to speed on how much date and time confusion there is, > I remember this article by Dave Rolsky as being interesting: > > http://www.perl.com/pub/a/2003/03/13/datetime.html You might also be interested in what Dave and others have

Re: Dates and Times

On Thu, 4 Mar 2004, TOGoS wrote: > > Actually, they did. UTC (which was the original > > reference) is defined such that noon is within .9 > > seconds of the sun being as directly overhead as > > it can be, and is thus directly tied to the > > behaviour of the planet. UTC may stop tracking UT1 an

Re: Dates and Times

On Sat, 6 Mar 2004, Jared Rhine wrote: > It'd be great, if possible, to get a statement here from the DateTime > group sanctioning one or another particular Parrot clock interfaces as > "efficient, complete, and preferred". I haven't poked over to see > if they are chatting about this Parrot issu

Re: Dates and Times

On Sat, 6 Mar 2004, Jared Rhine wrote: > It'd be nice if the first item, "gmclock" wasn't defined in terms of > "UTC". Regardless of the future fate of UTC leap seconds, any > UTC-based clock would need to account for leap seconds going back, > right? So it seems that GMT should be preferred in

Re: Dates and Times

On Tue, 9 Mar 2004, Edward S. Peschko wrote: > On Tue, Mar 09, 2004 at 04:21:24PM -0500, Gordon Henriksen wrote: > > "Not an opcode" doesn't mean "balkanized." There is a parrot/stdlib > > directory. > > fair enough, but then where does the distinction lie? Why put gmtime, et al. > in opcodes? As

Re: Dates and Times

On Tue, 9 Mar 2004, Edward S. Peschko wrote: > > >> This sort of creeping featuritis is why date formatting and especially > > >> parsing do NOT belong as opcodes. It's too big a problem to solve in the > > > > I agree. > > > And the more I think about it, the more I think this concern is misplace

.NET suitable for dynamic languages?

Hi Folks, I stumbled across a Slashdot story this morning titled "Super-Fast Python Implementation for .NET and Mono". With the Pie-thon just a couple of months away, I thought that this might be of interest (at least to Dan :). http://developers.slashdot.org/article.pl?sid=04/05/19/0128203&mo

Configure.pl warnings

Hi Folks, Configure.pl is giving me warnings about undef values being passed to C on my platform. -- $ perl Configure.pl . . Generating build filesdone. Moving platform files into place..Use of uninitialized val

bug #29268

Can someone close bug #29268 "failures in t/pmc/float.t on amd64"? It seems to have resolved itself. :) -J --

Re: [perl #37934] [TODO] build - log file

A log would be useful if it contained sufficient information to figure out why a test passed or failed. Similar to autoconf's config.log (an invaluable debugging tool when tracking down configuration problems). -J -- On Fri, Jan 11, 2008 at 12:51:11PM -0800, James Keenan via RT wrote: > Can some

Re: [perl #49762] [configure] JIT configuration problems on OS X

What is the OSX toolchain solution for inline asm with fat binaries? At some point we have to assume that people who are setting CFLAGS know what they are doing. We can't look for or protect against every silly thing they might do. Perhaps if --jitcapable is set and we're on darwin the thing to

Re: [perl #49762] [configure] JIT configuration problems on OS X

I found someone in my office with Leopard on their laptop. I'll try to take a stab at this over the weekend. -J -- On Tue, Jan 15, 2008 at 02:02:32PM +0900, Simon Cozens wrote: > Joshua Hoblitt via RT wrote: > >What is the OSX toolchain solution for inline asm wit

Re: [perl #38194] [TODO] build - optimize pmc2c.pl

James, Profiling is generally done with Devel::Profile. http://search.cpan.org/~jaw/Devel-Profile-1.05/Profile.pm Since pmc2c.pl is invoked so many times in the build process improving it's performance would sustainably speed up the overall build time. Cheers, -J -- On Mon, Mar 17, 2008 at 04

Re: [perl #38194] [TODO] build - optimize pmc2c.pl

On Sun, Mar 23, 2008 at 06:21:38PM -0700, James Keenan via RT wrote: > On Sat Mar 22 10:38:42 2008, doughera wrote: > > > Just be careful that 'use lib' doesn't look outside of the parrot source > > tree. If pmc2c.pl is normally invoked from the root directory, then > > ../lib and ../../lib are

Re: GCC 4.4

http://gcc.gnu.org/gcc-4.4/changes.html I'm sure the intel specific AES acceleration will come in real handy. ;) On Thu, May 08, 2008 at 10:39:29PM -0500, Andy Lester wrote: > I've just built the 5/2/2008 snapshot of GCC 4.4 and Parrot builds > fine on it. I wonder what new warning flags 4.4 h

Re: Call for B0rked

During OSCON, over beers with Chip, I made the observation that there is probably a large group of people that would like to contribute a few hours per work to Parrot development but that there are no TODO tasks that can be done reasonable accomplished at that level of commitment. Chip stated that

Re: Call for B0rked

Is it just me or is it b0rked to have a file named src/parrot.c that does nothing while the entry point for the parrot executable lives in imcc/main.c? -J -- On Wed, Aug 31, 2005 at 04:04:45PM -0700, chromatic wrote: > Hi all, > > In a recent discussion with Chip and Leo, the idea came up to ask

Re: [perl #37067] [PATCH] intro.pod - minor corrections

On Sun, Sep 04, 2005 at 01:58:16PM -0700, chromatic wrote: > For what it's worth, the Perl 5 policy is not to make UK English > speakers write US English and vice versa. Consistency within a document > is nice, though. A quick survey of ./docs suggests that the UK spelling is fairly consistently

Re: HLL Namespace Design

On Mon, Sep 05, 2005 at 01:43:20PM -0400, Matt Diephouse wrote: > Namespace Capabilities [ snip ] > - Querying Information > It must be possible to get a list of both variables and subroutines, > sometimes together and sometimes seperate. Just a quick addition to that: It must b

parrotbug - slow or size limits?

I submitted a patch to parrotbug about 4 hours ago and it hasn't shown up in RT yet nor have I received the auto-response email. The patch was rather large so I'm wondering if I haven't hit some sort of message size limit. Is this a normal lag or should I submit the patch directly through RT? Se

Re: [perl #37100] [PATCH] Pod tests + fixes

On Thu, Sep 08, 2005 at 12:12:18PM -0700, Bernhard Schmalhofer via RT wrote: > 't/doc/pod.t' also make a lot of sense. However could you comment on the > relation to t/perl/Parrot_Docs.t ? It looks like it checks the same > things as 'pod.t'. > I wonder whether it is worthwile to maintain Parrot::D

Re: [perl #37100] [PATCH] Pod tests + fixes

On Fri, Sep 09, 2005 at 02:26:04PM -0700, Bernhard Schmalhofer via RT wrote: > > [EMAIL PROTECTED] - Fr 09. Sep 2005, 02:15:03]: > > > > I completely missed the fact that Parrot_Docs.t even existed, DOH! > > Although, it looks like there would be no duplication of testing. The > > pod.t file I sub

Re: [perl #37100] [PATCH] Pod tests + fixes

On Fri, Sep 09, 2005 at 11:38:55AM -1000, Joshua Hoblitt wrote: > On Fri, Sep 09, 2005 at 02:26:04PM -0700, Bernhard Schmalhofer via RT wrote: > > I have committed the new test 't/doc/pod.t'. > > Great. Were the make targets left out on purpose? Nevermind. I can

Re: [perl #31980] Factorial example gives incorrect result

On Thu, Sep 08, 2005 at 01:43:35PM -0700, Bernhard Schmalhofer via RT wrote: > I have checked the factorial example on > http://www.parrotcode.org/examples/pasm.html. > > Starting with 13! incorrect results are indeed returned on my 32bit > Linux machine. I'm not surprised, the values listed on t

Re: [perl #31980] Factorial example gives incorrect result

On Sun, Sep 11, 2005 at 01:06:57PM +0200, Bernhard Schmalhofer wrote: > Well, the problem is that Parrot indeed returns the incorrect values > that are > mentioned in the webpage. I happen to get the correct answers out to 20! but only because I'm on 64bit hardware. The real issue is that the C

Re: [perl #31980] Factorial example gives incorrect result

-J -- On Sun, Sep 11, 2005 at 01:06:57PM +0200, Bernhard Schmalhofer wrote: > Well, the problem is that Parrot indeed returns the incorrect values > that are > mentioned in the webpage. I'd like to propose that we fix the n! values listed on the examples page, change the code example to the snip

Re: [perl #31980] Factorial example gives incorrect result

On Mon, Sep 12, 2005 at 07:24:47PM +0200, Bernhard Schmalhofer wrote: > I have added information on how to provide patches to > http://www.parrotcode.org > to docs/submissions.pod. > > Basically you create patches against > https://*svn*.perl.org/perl.org/docs/live/*parrotcode*/ >

Re: [perl #37100] [PATCH] Pod tests + fixes

On Sat, Sep 10, 2005 at 01:23:01PM +0200, Bernhard Schmalhofer wrote: > In ticket 37104 you mentioned spell checking with 'aspell'. Did you > encounter words > that were not in the aspell-en 6.0.0 dictionary? If so it could be > worthwile to a special aspell-dictionary to the Parrot distribution

Re: tcl in leo-ctx5

-- On Mon, Sep 12, 2005 at 04:54:17PM -0400, Will Coleda wrote: > Leo mentions on IRC that some tests are failing on i386 and OSX 10.3 > (10.2?). I'm passing 100% on OSX 10.4. > > Can we get some test results on other various platforms? (Do we have > a tinderbox again yet?) Tested with r9190.

Re: tcl in leo-ctx5

1 subtest UNEXPECTEDLY SUCCEEDED). Failed 4/47 test scripts, 91.49% okay. 11/445 subtests failed, 97.53% okay. make: *** [test] Error 255 -- -- $ uname -a Linux moanui 2.6.12-gentoo-r6 #1 Sat Jul 30 00:58:21 HST 2005 i686 Intel(R) Pentium(R) M processor 2.00GHz GenuineIntel GNU/Linux -- Cheers,

Re: tcl, exceptions in leo-ctx5

I can confirm that all tests are now passing on Linux/x86 with r9202. -- All tests successful. Files=47, Tests=446, 40 wallclock secs (28.78 cusr + 4.18 csys = 32.96 CPU) -- -J -- On Thu, Sep 15, 2005 at 05:24:09PM -0400, Will Coleda wrote: > Done. All tests pass for tcl in leo-ctx5. (And with

Re: [perl #16935] [PATCH] more regex stack manipulation

On Mon, Sep 19, 2005 at 09:57:24PM -0700, Sean O'Rourke via RT wrote: > "Joshua Hoblitt via RT" <[EMAIL PROTECTED]> writes: > > Since the rx_* ops are on the chopping block is there any objection to > > closing this bug? > > No objection from me. Ac

Re: [perl #16622] [PATCH PDD07] Document struct naming conventions

On Tue, Sep 20, 2005 at 12:33:38AM -0700, Brent 'Dax' Royal-Gordon wrote: > > > I submitted the patch below my sig way back in August 2002, in ticket > > > 16622. It documented the then-current naming conventions for > > > structures. Is it still accurate and/or a good idea? Should it (or an > >

Bug Wrangling

Hi Folks, You may have noticed lots of RT traffic on very old and stale bugs. What's going on is that I've foolishly volunteered to try to sweep out and tidy up Parrot's bug tracker. Living in the tropics has taught me the extreme importance of dealing with a bug problem before it gets out of han

Re: [perl #18097] [PATCH] allow NULL interpreter in sprintf like functions

On Tue, Sep 20, 2005 at 11:00:58AM +0200, Leopold Toetsch wrote: > > On Sep 20, 2005, at 7:42, Joshua Hoblitt via RT wrote: > > > > >Is this still an unresolved design issue or can the bug be closed? > > If in doubt just close such old [PATCH] tickets. I&#

Re: [perl #17490] Magic is useless unless verifiable.

On Wed, Sep 21, 2005 at 11:44:17AM +0100, Jonathan Worthington wrote: > "Joshua Hoblitt via RT" <[EMAIL PROTECTED]> wrote: > >>[jhoblitt - Mon Sep 19 22:28:00 2005]: > >> > >>> [EMAIL PROTECTED] - Sun Sep 22 07:13:56 2002]: > >>> &g

Re: [perl #17490] Magic is useless unless verifiable.

hange the packfile format, we > may as well make sure we're squeezing whatever use we can out of our magic > number. You raise a good question; how was the magic number chosen? > "Mark A. Biggar" <[EMAIL PROTECTED]> wrote: > >Joshua Hoblitt wrote: > > >

Re: [perl #25265] [PATCH] peek opcode

-- On Thu, Sep 22, 2005 at 05:47:31AM -0600, Cory Spencer wrote: > > >I'm closing this bug as 'rejected' because a corrected patch was never > >submitted. If you ever get it work, please do resubmit it. > > Actually, I believe it was eventually applied, although I'm not sure why > it wasn't upd

Call for IRIX testers - was Re: [perl #27003] bytecode (header?) problem in tru64/alpha

Does anyone has access to an IRIX machine? -J -- On Thu, Sep 22, 2005 at 07:37:44PM +0300, Jarkko Hietaniemi wrote: > > > > > Jarkko, > > > > Are there still outstanding issues on IRIX? AFAIK nobody else has been > > building parrot on that platform. > > Unfortunately I no more have access t

Re: [perl #17490] Magic is useless unless verifiable.

date by Jonathan Worthington C<[EMAIL PROTECTED]> +The header format was mangled by Joshua Hoblitt (JHOBLITT) C<[EMAIL PROTECTED]> + =head1 VERSION -2005.09.19 +2005.09.25 pgpJFB8PCFjfR.pgp Description: PGP signature

Re: [perl #17490] Magic is useless unless verifiable.

On Sun, Sep 25, 2005 at 09:43:15PM -0700, Chip Salzenberg wrote: > On Sun, Sep 25, 2005 at 10:04:16AM -1000, Joshua Hoblitt wrote: > > * The magic number is no longer an opcode outside the header. It is > > now an 8 byte magic string at the the beginning of the header. >

Re: [perl #22873] perldoc -U vs. perldoc -u

On Tue, Sep 27, 2005 at 11:31:17AM +0100, Peter Sinnott wrote: > On Mon, Sep 26, 2005 at 08:43:41PM -0700, Joshua Hoblitt via RT wrote: > > Does anyone have an old enough Perl to test if this is still an issue? > > > > -J > > > > -- > > parrot no lon

Re: [perl #24682] [BUG] How to handle divide by zero?

On Tue, Sep 27, 2005 at 01:50:55PM +0200, Leopold Toetsch wrote: > > SIGFPE with integer operations isn't portable and the discussion > concluded in: > explicit checks are better then relying on signals. > > I think it's resolved. > Were checks implemented or is this a TODO? -J -- pgpQnoUA

Re: [perl #17490] Magic is useless unless verifiable.

Jonathan, Chip gave an official OK via irc. <^conner> chip, Jonathan said that he'd try to do it as part of his changes and commit the doc patch when he's done ^conner: Oh, that's a good plan -J -- On Tue, Sep 27, 2005 at 12:13:06PM +0100, Jonathan Worthington wro

Re: [perl #17490] Magic is useless unless verifiable.

On Tue, Sep 27, 2005 at 01:49:52PM -0700, Chip Salzenberg wrote: > On Mon, Sep 26, 2005 at 03:29:52PM -1000, Joshua Hoblitt wrote: > > An updated patch is attached. > > All OK now with me, thanks. The ASCII art of the 'padding' was wrong. A corrected patch is atta

Re: [perl #37303] [PATCH] Relaxing parrot dependency on parrot_config

On Sat, Oct 01, 2005 at 10:26:21AM +0100, Nick Glencross wrote: > I'm not sure that the patch made it into RT. Here it is again, with a > small tweak to a Makefile dependency. It didn't make it in because I dropped the ball. Thanks for resubmitting. Cheers, -J -- pgpTSAwxJvVj8.pgp Descripti

Re: [perl #31285] [PATCH] first step in implementing a SCons base build

On Mon, Oct 03, 2005 at 03:49:25PM -0400, Matt Fowles wrote: > Joshua~ > > On 10/3/05, Joshua Hoblitt via RT <[EMAIL PROTECTED]> wrote: > > Matt, > > > > There has been alot of discussion about build systems on #parrot > > recently so I'm CCing p6i.

Re: [PATCH] Add BROKEN.pod

On Mon, Oct 03, 2005 at 06:17:30PM -0700, chromatic wrote: > > I'll check this in in two days with regard to feedback from anyone whose > opinion matters and what to call it and where to put it, if my initial > choice isn't perfect. I'm wondering if this wouldn't be better split up into RT ticket

Re: [PATCH] Add BROKEN.pod

On Tue, Oct 04, 2005 at 06:30:05PM +0200, Leopold Toetsch wrote: > > There are 2 philosophies amongst people: some prefer RT, others prefer > one document in the tree. The goal could be to auto-create BROKEN from > RT tickets then. (I prefer one file, btw ;-) That shouldn't be too hard with the

Re: [perl #36098] Solaris - Large number of tests fail under jit

On Wed, Oct 05, 2005 at 01:45:24AM -0700, Peter Sinnott via RT wrote: > On Tue, Oct 04, 2005 at 09:04:57PM -0700, Joshua Hoblitt via RT wrote: > > I do not have access to the same machine any longer so I have retested > with solaris 2.8 , gcc 3.2.1 and the 2005-10-05_071500 parro

Re: [PATCH] Add BROKEN.pod

On Wed, Oct 05, 2005 at 03:01:35PM -0700, chromatic wrote: > On Mon, 2005-10-03 at 17:05 -1000, Joshua Hoblitt wrote: > > > I'm wondering if this wouldn't be better split up into RT tickets > > similar to the way TODOs are handled. Having everything in one coherent

Re: [perl #36200] Parrot on Linux/m68k test failures

On Wed, Oct 05, 2005 at 09:22:34PM -0700, Joshua Juran via RT wrote: > Parrot itself builds successfully, but 'make' fails here: > > ... > ./parrot -o runtime/parrot/library/Stream/Sub.pbc > runtime/parrot/library/Stream/Sub.imc > ./parrot -o runtime/parrot/library/Stream/Writer.pbc > runtime/pa

Re: [PATCH] Re: [perl #37334] AutoReply: [PATCH] Parrot 0.3.0 does not compile in Tru64 because of missing socklen_t

On Thu, Oct 06, 2005 at 08:20:22AM +0300, Jarkko Hietaniemi wrote: > > > --- config/init/hints/dec_osf.pl.dist 2005-10-05 20:29:30.0 +0300 > > +++ config/init/hints/dec_osf.pl2005-10-05 20:31:25.0 +0300 > > @@ -6,6 +6,10 @@ > > if ( $ccflags !~ /-pthread/ ) { > > $c

  1   2   3   >