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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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?
> >
>
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
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
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
>
> --
pgpht9olpUBmS.pgp
Description: PGP signature
This is Martin Michlmayr Ph.d thesis:
http://www.cyrius.com/publications/michlmayr-phd.pdf
-J
--
pgpBoYLGg19Mn.pgp
Description: PGP signature
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"
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
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
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
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
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
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
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
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
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
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/
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
>
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
--
pgp5clC56Bbat.pgp
Description: PGP signature
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
On Mon, Aug 21, 2006 at 12:06:36AM +0100, Andrew Suffield wrote:
> On Sun, Aug 20, 2006 at 03:55:56PM -0600, Luke Palmer wrote:
>
> > Why would you care about introducing a new lexical scope? You would
> > care about that if you used a variable you declared in the commented
> > code in the code b
On Sat, Aug 19, 2006 at 02:26:28AM +, Luke Palmer wrote:
> On 8/19/06, Aaron Crane <[EMAIL PROTECTED]> wrote:
> >You don't actually need a macro in that case:
> >
> >if 0 { q<
> >...
> >> }
>
> Which, of course, eliminates the original desire to have a
> code-commenting constru
It occurred to me that other day that in our "in house" C code we
somewhat frequently use an idiom that's not easily translated into Perl
5. Our rule is that if your commenting out more then 1 or 2 lines of
code that you wrap it in a CPP if statement. The logic being that
if you haven't deleted t
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)
> +
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
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 >
A significant portion of parrots build time is spent running
tools/build/pmc2c.pl & tools/build/c2str.pl. Neither of these programs
loads Parrot::Config and there isn't/shouldn't be any system dependent
behavior. Does it make sense for the code generation to be a
--maintainer processes only?
-J
On Tue, Aug 01, 2006 at 10:29:52PM -0500, Chris Dolan wrote:
> On Aug 1, 2006, at 2:45 PM, Joshua Hoblitt wrote:
>
> >While I'd been hoping that M::B had a public method for changing
> >'blib'
> >this appears not to be the case (just looking at the pod).
On Tue, Aug 01, 2006 at 12:30:28PM -0700, chromatic wrote:
> On Tuesday 01 August 2006 12:24, Joshua Hoblitt wrote:
> > I'd say let Module::Build handle the install. The install process can
> > invoke Module::Build if it's to be part of the default install.
>
&g
On Mon, Jul 31, 2006 at 10:30:36PM -0700, chromatic wrote:
> * What's the best way to integrate building this module from the main
> Makefile? Should it be part of that process?
That depends. Are any of the standard regression tests going to require
this module?
> * Where should the built modu
I'd like to see PPD 25 "threads" reviewed. The ruff API isn't even
layed out in this document -- is there supposed to be a thread PMC or
what? I'm also concerned about the performance impact of having to
always check if a PMC is shared and having to spin a mutex if it is. At
a minimum it should
On Fri, Jul 21, 2006 at 03:04:06PM -0400, Mr. Shawn H. Corey wrote:
> Determining if your C compiler is actually gcc.yes.
> Determining if your C compiler is actually Visual C++...no.
> Enabling optimization...n
I believe ambs & I fixed this before the bug was filed. ;)
-J
--
On Tue, Jul 18, 2006 at 01:31:16PM -0700, Chip Salzenberg wrote:
> # New Ticket Created by Chip Salzenberg
> # Please include the string: [perl #39867]
> # in the subject line of all future correspondence about this issue.
> # h
On Tue, Jul 18, 2006 at 01:38:20AM -0700, Allison Randal wrote:
> [EMAIL PROTECTED] wrote:
> >
> >* However, the bison interface does not support both "interp"
> > and "yyscanner" as flex inputs; so I created a patch file
> > at compiler/imcc/imcparser.c.diff -- it needs to be applied
> > manual
On Mon, Jul 17, 2006 at 12:11:55PM -0700, chromatic wrote:
> After discussing the idea with Allison, we both believe that Parrot should be
> able to produce a single PBC file from a command like:
>
> parrot -o all_files.pbc file1.pir file2.pir ... filen.pir
It'd probably make sense to defi
4th Option: fix flex. ;)
-J
--
On Sun, Jul 16, 2006 at 10:57:07PM -0500, Vishal Soni wrote:
> Hi,
>
> Please disregard the previous mail. Hit the wrong shortcut key!!
>
> I have been working on trying to make reenterant and/or thread-safe. There
> are couple of things that have come up which mi
On Sat, Jul 08, 2006 at 07:01:19PM -0500, Steven Pritchard wrote:
> First, there is a hardcoded "lib" somewhere that I can't seem to find.
> On x86_64, libraries should get dropped in /usr/lib64, but "make
> install" never creates /usr/lib64/parrot. Pointers on how to override
> that would be grea
Steve,
What version of OpenBSD were you running (perhaps something old or
direct from CVS)?
-J
--
On Tue, Mar 21, 2006 at 03:13:18PM -0800, Joshua Isom via RT wrote:
> On OpenBSD 3.8 x86, I still get the failures with -0.0/0.0. Check the
> smokes...
>
> On Mar 21, 2006, at 3:0
On Tue, Mar 21, 2006 at 06:42:42AM -0800, Steve Peters via RT wrote:
> > [jhoblitt - Sun Jan 01 18:49:23 2006]:
> >
> > I've commited a possible fix for openbsd, cygwin, & solaris as
> changesets
> > r10839 & r10843. I basically applied what Steve Peters proposed but
> > with the changes in mat
On Tue, Feb 21, 2006 at 08:06:18AM -0500, Will Coleda wrote:
>
> On Feb 21, 2006, at 4:29 AM, Joshua Hoblitt wrote:
>
> >I don't believe that this is the correct solution. The 'parrot'
> >binary
> >needs to be linked to the correct library. Curren
trick would be far messier, i.e. have parrot load
> libparrot.dylib instead of link against it.
>
> On Feb 20, 2006, at 7:17 PM, Joshua Hoblitt wrote:
>
> >Is there some reason that this can't be a -L flag passed to CC? IMHO -
> >it's bad policy to go littering makefile wi
Is there some reason that this can't be a -L flag passed to CC? IMHO -
it's bad policy to go littering makefile with env variable declaration
as the effect is global until the end of the makefile.
-J
--
On Mon, Feb 20, 2006 at 06:40:24PM -0600, Joshua Isom wrote:
> It was working on 11676, and I
On Tue, Feb 21, 2006 at 01:03:59AM +0100, Leopold Toetsch wrote:
>
> On Feb 20, 2006, at 23:44, Joshua Hoblitt via RT wrote:
>
> >What happened to the factorial PASM example? It seems to have
> >disappeared and it hasn't re-appeared as a PIR example either.
>
On Tue, Feb 21, 2006 at 01:02:23AM +0100, Leopold Toetsch wrote:
>
> On Feb 20, 2006, at 23:28, Joshua Hoblitt via RT wrote:
>
> >Is this really worth doing? Since profiling flags are compiler
> >specific
> >isn't it better to just let them be set as additio
On Tue, Feb 21, 2006 at 01:01:11AM +0100, Leopold Toetsch wrote:
>
> On Feb 20, 2006, at 23:25, Joshua Hoblitt via RT wrote:
>
> >This flag is in use by the inter::exp step but it's not doing much.
> >Should this flag be kept or not?
>
> I'd remove it,
On Tue, Feb 21, 2006 at 10:06:36AM +1100, Sisyphus wrote:
> Yes, /usr/local/lib is already in /etc/ld.so.conf.
Perhaps you need to run `ldconfig` as root.
> $LD_LIBRARY_PATH is initially empty. If I don't add '/usr/local/lib' to it,
> then when I run 'parrot hello.pir', I get (transcribed):
>
>
What happened to the factorial PASM example? It seems to have
disappeared and it hasn't re-appeared as a PIR example either.
-J
--
No one ever made any actualy attempt to impliment the build in scons,
makepp, etc. and since we're moving towards Configure in PASM/miniparrot
I'm going to close out this bug.
-J
--
> [EMAIL PROTECTED] - Wed Dec 29 18:22:10 2004]:
>
>
> This code:
>
> new P0, .Undef
> new P1, .Undef
> eq P0, P1, L1
> print "not "
> L1: print "ok\n"
> end
>
> prints "not ok". Should it? If Parrot considers every Undef PMC to
> be distinct, it's going to ma
> [coke - Sun Aug 15 13:41:43 2004]:
>
> Add profiling build options
>
> (From the TODO file)
>
>
Is this really worth doing? Since profiling flags are compiler specific
isn't it better to just let them be set as additional CFLAGS?
-J
--
This flag is in use by the inter::exp step but it's not doing much.
Should this flag be kept or not?
-J
--
On Sun, Feb 19, 2006 at 03:28:32PM -0800, Leopold Toetsch wrote:
> *) jit2h.pl doesn't create a .h file - a better util name couldn't harm
I've renamed it to jit2c.pl and added a JIT_BUILD_TOOL var in the root
makefile so the path of this utility is no longer repeated encoded.
-J
--
pgpKmgEPz
On Fri, Feb 17, 2006 at 05:23:55PM -0500, Andy Dougherty wrote:
> On Fri, 17 Feb 2006, jesse wrote:
> > Do you, perchance, sit behind an http proxy server?
>
> Not that I know of (though I'm not sure how I'd know), and no other mode
> of communication is similarly affected (i.e. cvs, rsync, etc.,
As of r11568 all configuration step's ->runstep() method is required to
return $self unless it wants to indicate a fatal error. An error string
is expected to be returned via the ->result() method. The steps we're
previously changed to conform to this behavior but Parrot::Configure now
requires i
Is this bug resolved? If not, what platforms is it still failing on?
-J
--
> [doughera - Mon Feb 13 09:10:50 2006]:
>
> On Fri, 10 Feb 2006, Allison Randal wrote:
>
> > On Feb 10, 2006, at 9:56, Andy Dougherty via RT wrote:
> > >
> > > I too had seen this memory problem before on Solaris/SPAR
This bug seems to have resolved itself at least on amd64/linux. Please
re-open this bug if it's still failing for you. Thanks for reporting.
-J
--
This bug seems to have resolved itself.
-J
--
Please resolve patch bugs after applying the patch.
-J
--
Just a quick reminder devs as to that to do when you apply a patch.
You need to:
Take ownership of the bug
Set the patch status to Applied
***Set the Status to resolved***
If nothing else, please at least set the Status to resolved so someone
else doesn't have to clean up the bug trac
There were a large number of open and owner-less bugs in the Parrot bug
queue (48 after a cleaning up about half a dozen). I've changed the
status on all of these bugs to 'new' as it's really not appropriate to
have open and ownerless bugs (can we change RT's behavior to stop change
the status to
;
>
>
>
> On Feb 15, 2006, at 5:41 PM, Joshua Hoblitt wrote:
>
> >On Tue, Feb 14, 2006 at 11:52:55PM -1000, Joshua Hoblitt wrote:
> >>On Tue, Feb 14, 2006 at 05:23:39PM -0800, Will Coleda wrote:
> >>>2) checks every file with pod in that direct
;s a suggested alternative that fails fast
> instead of slow if *either* module isn't installed, and includes your
> changes.
>
>
>
>
>
> On Feb 15, 2006, at 5:41 PM, Joshua Hoblitt wrote:
>
> >On Tue, Feb 14, 2006 at 11:52:55PM -1000, Joshua Hoblitt
On Tue, Feb 14, 2006 at 11:52:55PM -1000, Joshua Hoblitt wrote:
> On Tue, Feb 14, 2006 at 05:23:39PM -0800, Will Coleda wrote:
> > 2) checks every file with pod in that directory hierarchy.
> >
> > It should only check those files that are in MANIFEST. (And
> > *p
On Tue, Feb 14, 2006 at 05:23:39PM -0800, Will Coleda wrote:
> t/doc/pod.t currently:
>
> 1) starts checking from the current directory.
>
> It should start at the parrot root based on Parrot::Config
Fixed in r11551.
> 2) checks every file with pod in that directory hierarchy.
>
> It should on
On Mon, Feb 13, 2006 at 08:09:45PM -, Jonathan Worthington wrote:
> "Joshua Hoblitt" <[EMAIL PROTECTED]> wrote:
> >I think your slightly confusing OPs and PMCs. Presumably the *dir
> >functionality would be implemented as OP codes
> >
> I thought The
On Mon, Feb 13, 2006 at 09:28:40AM -0600, Chris Dolan wrote:
> On Feb 12, 2006, at 6:52 PM, Joshua Hoblitt wrote:
>
> >It would also be 'really nice' have a glob(3) like method that is
> >implemented as a wrapper around *dir methods so the semantics are
> >por
On Mon, Feb 13, 2006 at 12:23:33AM +0100, Leopold Toetsch wrote:
>
> On Feb 12, 2006, at 21:13, Alberto Sim?es wrote:
>
> >Applied as r11511 (wow, a palindrome revision :-))
>
> And reverted in r11512 by ambs. The choosen method name isn't, well,
> the best choice, the used OS calls (opendir/re
About a month ago I wrote a example configuration step to show off the
new capability of passing arguments to a step from Configure.pl. It
seems that I forgot to send out an e-mail about this...
The example step is called gen:PodTex and creates plain text files from
Pod documents with Pod::Text.
The the darwin hints and MANIFEST.generated changes look OK but the
root.in changes will review some more review.
As a side note it's pretty clear that MANIFEST.generated needs to be
machine generated itself.
-J
--
On Wed, Feb 01, 2006 at 04:53:46PM -0800, Joshua Isom wrote:
> # New Ticket Creat
On Thu, Jan 26, 2006 at 07:18:55PM +, Nicholas Clark wrote:
> On Thu, Jan 26, 2006 at 03:22:11PM +0800, Steve Gunnell wrote:
>
> > 5) Seeking through an encoding filter could be highly problematic.
> > Filters such as "utf8" that have a non-deterministic byte per character
> > ratio should pol
On Wed, Jan 25, 2006 at 10:24:51PM +, Alberto Sim?es wrote:
> For me, both options are reasonable. Chip's proposal have the advantage
> of caching the info. Using is_dir and is_file to stat everytime, have
> the advantage of not having a specific Stat PMC object.
> Other option, is having one
On Mon, Jan 23, 2006 at 12:13:50AM +, Nick Glencross wrote:
> Nick Glencross wrote:
>
> >There seem to be a few recent events which can now trigger a newish
> >problem:
> >
>
>
> >The real problem is that -L/usr/local/lib is brought in from parrot,
> >so we have a few choices:
> >
> > *
On Tue, Jan 17, 2006 at 04:55:36PM -0800, jerry gay wrote:
> i think that better answer should be in the form of CPAN bundles. a
> development bundle (Bundle::Parrot::Devel), a test bundle (::Test),
> perhaps a seperate smoke bundle (::Smoke), and perhaps a bundle for
> end users (::Install.)
The
On Tue, Jan 17, 2006 at 12:44:56PM -0800, jerry gay wrote:
> attached is my lib/Parrot/Config.pm file generated from r11223, on
> windows using msvc. inside you'll find a few things, like keys given
> unix file path values,
> 'bin_dir' => '/usr/local/bin',
>
> an invalid key,
>
Bernhard++
-J
--
On Tue, Jan 17, 2006 at 09:55:47PM +0100, Bernhard Schmalhofer wrote:
> It looks like the script 'tools/dev/genrpt.pl' does basically the same as
> 'parrotbug'.
> In order to decrease the level of confusion I propose to remove
> genrpt.pl and the associated make targets 'ok', 'o
Per step parameter support implimented in r11203.
-J
--
Bernhard++
-J
--
On Sat, Jan 14, 2006 at 05:01:23AM -0800, Bernhard Schmalhofer wrote:
> # New Ticket Created by Bernhard Schmalhofer
> # Please include the string: [perl #38235]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.
On Fri, Jan 13, 2006 at 02:59:44PM -0800, Joshua Isom wrote:
>
> There are a fair number of documentation files in parrot that are pod
> files. Most of the README files aren't pod files, but the pge README
> and the tcl README are. There are several other files where the same
> occurs. If th
On Thu, Jan 12, 2006 at 11:11:13AM -1000, Joshua Hoblitt wrote:
> On Thu, Jan 12, 2006 at 07:51:58PM +, Nick Glencross wrote:
>
> > It looks like only prefix is actually set, and the other paths are set
> > using pkgconfig variables (which look the same as the style th
On Thu, Jan 12, 2006 at 04:53:26PM +0100, Leopold Toetsch wrote:
> Klaas-Jan Stol wrote:
> >Hi,
> >
> >I'm trying to implement some functions into the Lua PMCs, but I'm having
> >trouble to compile them.
> >
> >I want to add a clone method to the LuaNil PMC (which should extend
> >Null.pmc, not N
I'd vote for that being the default method that can be overridden on a
per platform basis with a more functional/efficient version.
-J
--
On Thu, Jan 12, 2006 at 12:07:33PM +, Alberto Manuel Brand?o Sim?es wrote:
> I'm not implementing copy at the moment as I lack knowledge. I might
> just w
On Thu, Jan 12, 2006 at 07:51:58PM +, Nick Glencross wrote:
> It looks like only prefix is actually set, and the other paths are set
> using pkgconfig variables (which look the same as the style that we've
> just moved away from).
>
> I hope that you don't mind, but I've not used your patc
The ${foo} interoplation/substitution syntax is no more. It has been
replaced with the autoconf like @foo@ syntax and all of the *.in files
have been updated. The special quoting syntax has also been removed
from parrot.pc.in
Support implimented in r11082 & r7.
Cheers,
-J
--
$ perl t/harness t/library/getopt_obj.t
t/library/getopt_objNOK 13
# Failed test (t/library/getopt_obj.t at line 559)
# got: '"argv" => ResizablePMCArray (size:7) [
# "--ignored",
# "-i",
# "--ignored=hello",
# "argv",
# "stay",
# "-",
# "with me"
# ]
#
Please reopen this bug if we're still screwing up the CPAN indexer after
the next release. Thanks for bringing up this issue.
Cheers,
-J
--
> [EMAIL PROTECTED] - Sun Jan 01 18:44:33 2006]:
>
> Parrot::Configure::Step::genfile() currently interpolates values in the
> format ${foo}. This is undesirable because ${ BAREWORD } is valid perl5
> syntax and in make files it looks uncomfortable similar to $(foo). It
> should be changed to @f
1 - 100 of 280 matches
Mail list logo
