The Perl::Critic testing in t/codingstd/perlcritic.t needs to be
optional. The existence of Perl::Critic on a machine doesn't mean
that it's appropriate to run Perl::Critic on the Parrot code.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jun 27, 2007, at 3:22 PM, Andy Lester wrote:
The Perl::Critic testing in t/codingstd/perlcritic.t needs to be
optional. The existence of Perl::Critic on a machine doesn't mean
that it's appropriate to run Perl::Critic on the Parrot code.
Following up, it takes almost 11 un
On Jun 27, 2007, at 11:50 PM, chromatic wrote:
I'd like to see an option to run it only on *modified* files.
Modified since when?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
on a given VCS. I know
Parrot's hosted in Subversion, but what about the Git folks?
It smells funny to me.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jun 28, 2007, at 12:52 AM, chromatic wrote:
Heck, you didn't
even *compile* before one of your checkins yesterday.
Yeah, I did. I just had modified something else on a wild tear,
forgot to revert it, and did a commit hours later. Sorry about that.
--
Andy Lester => [EMAIL P
sults, too. That's what we do at work,
and it's annoying, but it's there and it's pretty in-your-face.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
;n'replace. My only
fear was that INTERP meant something different.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
lfoundation.org/hackathon-chicago/ -- The 2006
hackathon in Chicago
* http://www.perlfoundation.org/hackathon-toronto/ -- The 2007
hackathon in Toronto
Thanks to Socialtext for the hosting.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Of course! We #define interp NULL!
AAAAGHHHH
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
portability problem)
CCWARN="-Wall"
perl Configure.pl \
--cc="$CC" \
--cxx="$CX" \
--link="$CX" \
--ld="$CX" \
--ccflags="$CCFLAGS" \
--ccwarn="$CCWARN" \
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
http://www.perlfoundation.org/parrot/index.cgi?headerizer
I've started this page as my brain dump of ideas until I get it into
a proper .pod file. Please add to it, or ask questions on the page,
as you see fit.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.p
id is fine. In English
text, it's not.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
t these are indeed gcc-specific? Thanks.
Yes. They are gcc-specific. A plain -p is common on Unix systems, but
-pg is gcc-specific. For example, with Sun's C compiler, -xpg would be
the equivalent flag. (Though Sun's C compiler also has other profile
options selected by -xprofile. I
work.
That I can't tell. All I'm looking at is the underlying C code,
where it seems to me that passing in a rep of NULL should not be
allowed.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Thank you so much for hosting these wikis up to now! (Also, thanks
Socialtext for the ongoing hosting)
Thanks for sayin'. That's the problem with JFDI, is you get stuck
with what you D.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I've set up a box at home running Solaris 10 with Sun Studio 12. If
anyone wants an account on it so that they can work on the platform,
let me know, preferably in IRC.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
not NULL.
If I don't hear anything, I'll go ahead and do this tonight or tomorrow.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
="$CC" \
--link="$CC" \
--ld="$CC" \
--ccflags="$CCFLAGS" \
--ccwarn="$CCWARN" \
I'm working on linker hints right now.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
n. I think GCC just aggravates it.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ous tools at our disposal
when I get it working.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 9, 2007, at 7:16 PM, James E Keenan wrote:
Can you give us splint noobs a rundown on how to interpret this
data? Thanks.
Give us another couple of days to shake out the noise, 'kay?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ic append syntax and then use it (if needed) for
ccflags.
I'm also advocating revising the hints file so the append syntax isn't
needed!
--
Andy Dougherty [EMAIL PROTECTED]
ve their own str_dup do.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
you
have to add it manually.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
.2
Hi Andy,
I've updated the source code distribution to 3.1.2 (which is posted
now on splint.org), to incorporate the latest CVS version (with a
few more minor fixes). The CVS code and source code distribution
are now the same.
Thanks for the prodding, I should have done this a lo
Can y'all please go update this page and talk about what platforms
you're using? I can never keep track of who's doing what.
http://www.perlfoundation.org/parrot/index.cgi?platforms
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
se
macros are good, and consting is good, and all the seat belts I'm
trying to put in place. I'm thinking a new doc is in order.
Thoughts?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ils.
Alas, I'll be leaving on Friday but will be around on Sunday before
OSCON. Will anyone else be available for pre-OSCON hacking?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ey might be pretty far out in my mind to remember.
The Perl 5 codebase is RADICALLY different from the Parrot one, thank
goodness.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 17, 2007, at 3:48 PM, David Maxwell wrote:
Hello Andy,
Paul Cochrane asked me to set up a login for you in the Parrot Scan.
Since each project is a seperate instance of Coverity Prevent, logins
aren't shared between them - so this account is completely seperate
from
your
There's a p5 reposithon going on at Schwern's before OSCON. I'd like
to hook up with Jonathan and whoever else is around pre-OSCON there,
and have our own little Parrot hackathon on the corner. I'm sure
Schwern will be fine with that.
--
Andy Lester
ost of all I wanted to be able to make it to both hackathons.
Then again, if it's just me & Jonathan, how much of a hackathon is that?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Name Uninspected Bug False Ignore Pending Resolved
Total
parrot-0.4.13 722 0 0 0 7 81
Those 7 are all from me, I believe. The bugs are in RT. The rest
I'm not sure about yet. I'm plodding through as I have time.
Log:
[Coverity] USE_AFTER_FREE, set pointer to NULL after free so it
could be returned safely.
Excellent! Are you marking it in the Coverity system as RESOLVED?
Thanks,
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 22, 2007, at 9:01 AM, [EMAIL PROTECTED] wrote:
[Coverity] CID:67 USE_AFTER_FREE - reordered statements to correct
problem
I can't tell you how happy it makes me to see these.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 23, 2007, at 7:21 PM, chromatic wrote:
I'm okay with that, but we should also decorate PANIC with
PARROT_DOES_NOT_RETURN, which I believe *should* help compilers.
I'm all over it, long ago. PANIC just wraps do_panic which is so
decorated.
--
Andy Lester => [EM
On Jul 23, 2007, at 5:57 PM, Kevin Tew wrote:
My thinking was that, should someone, someday change PANIC into a
recoverable error, this will prevent leakage.
Ok its a stretch. :)
if it's unreachable, we need to get rid of it. PANIC is a dead-end.
xoa
--
Andy Lester => [EMAIL P
5 1280 160 155 1-37 39-70 72
74-90 92-
96 98-160
t/pmc/exporter.t 6 1536126 1-6
t/pmc/objects.t1 25678 77 1-6 8-78
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 24, 2007, at 8:43 AM, Andy Lester wrote:
Here's what I know is broken because of changes I've made yesterday:
t/compilers/imcc/syn/file.t 255 6528013 16 1-13
This is still broken, as is shootout (of course).
t/library/test_builder_tester.t0 612
as much as
possible.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
an be (PMC)NULL or it can be PMCNULL, a special non-
null variable.
See how it's defined in the header.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Because PMCNULL can be (PMC)NULL or it can be PMCNULL, a special non-
null variable.
See how it's defined in the header.
I thought we fixed it. Let's fix it.
I don't know what the broken is. We don't want a special PMCNULL
value? What is the backstory on PMCNU
PMCNULL is a singleton Null PMC. It's good. We like it. Hooray
for PMCNULL.
Except that PMCNULL is not a real NULL and therefore splint and lint
and whatnot can't keep track of it getting somewhere it shouldn't be.
--
Andy Lester => [EMAIL PROTECTED] =
On Jul 25, 2007, at 11:06 PM, chromatic wrote:
or remote, I can go either way) or to mark failing tests as TODO
before
checkin if you know they're going to fail?
Duh, duh, duh. I forgot about TODOs. Yeah, I'll do that.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] =>
Andy also needs we need a pbc disassembler where it dumps .pbc to
pasm, if we don't have one.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Josh putting in the new backtrace behind my new assertions makes
debugging assertions SO MUCH EASIER.
I'm gonna go s/assert/PARROT_ASSERT/ everywhere.
xoxo,
Andy
P.S. sample
# Received:
# 1..1
# Backtrace - Obtained 16 stack frames (max trace depth is 32).
# (un
the
pointers that it says are unprotected.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jul 30, 2007, at 9:56 PM, Mark Glines wrote:
Also note that PDD07 actually has two header guard examples; grep for
PARROT__H_GUARD and grep for PARROT_FOO_H_GUARD. I think
these should be consolidated as well, but this patch does not address
that.
Done and committed. Thanks.
--
Andy
er spots in parrot where floating point comparisons
are being made for other reasons. For those, you may indeed want to ask
how precise the comparison ought to be, but I expect those are quite rare.
--
Andy Dougherty [EMAIL PROTECTED]
0;
The REAL question, I believe, is for comparisons to zero. Last ptc
and I talked about this, there were no places where the comparison in
question isn't against 0.0.
Should simplify things a lot.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Aug 1, 2007, at 2:29 AM, Paul Cochrane wrote:
After some more testing that seems correct. Andy mentioned to me
yesterday about configuring with --cgoto=0 and this allows parrot to
compile on Solaris with suncc.
Yet another example where we need to be working on compilers, not
platforms
I just committed a patch that autodetects the HASATTRIBUTE_xxx
attributes for GCC. It's kinda funky under Solaris, but still passes.
Please let me know what happens on other platforms. I'm off to bed.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
y well
defined.
This whole discussion seems pointless. The accuracy of floating point
calculations depends sensitively on what, precisely, the programmer is
attempting to do. Guessing programmer intent doesn't seem to me to be an
appropriate job for a virtual machine.
--
Andy Dougherty [EMAIL PROTECTED]
> happier, which made me wonder if it worked on other platforms (it
> > > seemed to) and hence why I asked. Better safe than sorry :-)
> >
> > I think only GCC can compile the computed goto core. Certainly Visual
> > Studio
> > can't, and it doesn't
e the autosniffing I've done on
the HASATTRIBUTE flags.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
t;
> my %eval = eval cc_run();
> return if !%eval;
Have you looked at the string it returns? It looks like this:
(
GCC_VERSION => 3,
GCC_MINOR => 4
);
Or something similar. It perplexed me as well.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
things out
similarly on x86_64.
~jerry
Does MS provide any cheapie installs of their compiler? I now have
WinXP running on my Mac laptop and it would be swell if I could do
builds on MSVC, too.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On 7 Aug 2007, at 15:51, Andy Lester wrote:
Does MS provide any cheapie installs of their compiler? I now have
WinXP running on my Mac laptop and it would be swell if I could do
builds on MSVC, too.
This any use?
http://msdn.microsoft.com/vstudio/express/
--
Andy Armstrong, hexten.net
On Aug 7, 2007, at 10:25 AM, Andy Armstrong wrote:
This any use?
http://msdn.microsoft.com/vstudio/express/
Beautiful. Sure looks like it.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
implementing them. I also
removed some now unnecessary #includes"parrot/compiler.h" statements and
cc_inc fiddling in config/init/hints/solaris.pm
There should be no functional changes.
diff -r -u parrot-orig/config/auto/attributes.pm
parrot-andy/config/auto/attributes.pm
--- parrot
? For the decorators to really make sense, we need both halves of
the equation.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
des the default
ones that already exists? That's what I'm thinking of.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Aug 8, 2007, at 10:58 AM, [EMAIL PROTECTED] wrote:
-static PMC* undef(Interp* interp)
+static PMC *undef(Interp *interp)
And this should get changed to
static PMC *undef(PARROT_INTERP)
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
PMC* get_pmc_keyed(PMC *key) {
+PMC *get_pmc_keyed(PMC *key) {
Hash *hash = (Hash *)PMC_struct_val(SELF);
if ((PObj_get_FLAGS(key) & KEY_type_FLAGS) ==
PObj_get_FLAGS(key) is effectively a NOTNULL on key, so you can make
the parm for get_pmc_keyed be NOTNULL(PMC *key).
Thanks,
x
ist to help you on this (assuming you're
doing this in PHP).
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
its permanent home.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Aug 11, 2007, at 10:11 AM, Bob Rogers wrote:
All tests pass, so this is purely at the annoyance level. I'm running
gcc 3.3.1; is it because that is too old?
No, the autodetection doesn't do all we want yet.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I don't have a gcc 3.3 anywhere. Any of you got one I can get to?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ased the size of my 'make' output log by a factor
> of 100 -- though it has no affect, AFAICT, on anything happening in 'make
> test'. It is really f*!#$%ing annoying, isn't it.
>
I'm not sure if it's relevant, but this attribute is available with
gcc-3.3,
On Mon, 13 Aug 2007, Andy Dougherty wrote:
> On Sat, 11 Aug 2007, James E Keenan wrote:
>
> > Bob Rogers wrote:
> > >Compiling r20605 last night gave me 69291 occurrences of a warning
> > > about warn_unused_result:
> > >
> > > include/
On Aug 14, 2007, at 6:27 PM, Andy Dougherty wrote:
see above. It would have been nice if gcc simply rejected the
attribute
so that testing the exit status of gcc would be sufficient. gcc-3.4
doesn't have this problem. The test could either be made to only work
for gcc > 3.3, or
On Tue, 14 Aug 2007, Andy Lester wrote:
> On Aug 14, 2007, at 6:27 PM, Andy Dougherty wrote:
>
> > see above. It would have been nice if gcc simply rejected the attribute
> > so that testing the exit status of gcc would be sufficient. gcc-3.4
> > doesn't have
getting their own, but why is 3000 lines a bad thing?
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
arning
should simply be turned off. It isn't doing anything useful here.
--
Andy Dougherty [EMAIL PROTECTED]
On Sun, 19 Aug 2007, chromatic wrote:
> On Sunday 19 August 2007 17:32:01 Andy Dougherty wrote:
>
> > On Sat, 18 Aug 2007, [EMAIL PROTECTED] wrote:
>
> > > Log:
> > > Added FLOAT_IS_ZERO() macro to parrot/misc.h for comparing floats to
> > > zero. This
On Mon, 20 Aug 2007, Nicholas Clark wrote:
> On Mon, Aug 20, 2007 at 10:18:33AM -0400, Andy Dougherty wrote:
> > Your trick (extended, if needed, by clever Configure.pl probes) will
> > cleverly suppress the warning for the f == 0 case, while still retaining
> > the exact co
Tue Aug 21 11:39:01 2007
+++ parrot-andy/PLATFORMS Tue Aug 21 11:36:52 2007
@@ -26,10 +26,10 @@
linux-x86_64-gcc4.1.0 4 Y-- Y Y YY/2 ?
20060807
linux-x86_64-gcc4.1.2 8 Y-- Y Y YY ?
20070619
openbsd-zaurus-gcc3.3.5
http://perlbuzz.com/2007/08/statistical-views-of-open-source-projects-
on-ohloh.html
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
hints/linux.pm that will probably trigger the same problem.
--- parrot-current/config/init/hints/linux.pm Tue Aug 14 16:06:54 2007
+++ parrot-andy/config/init/hints/linux.pm Wed Aug 29 09:09:00 2007
@@ -69,6 +69,34 @@
$cc_flags .= ' -D_GNU_SOURCE';
}
+### XXX Thi
er
either selected the correct compiler or needs to know if it's the wrong
compiler. You can't feed it a random wrong value and expect it to still
pass.
You can test this for yourself by applying the linux hints file patch I
posted in RT #45025 and changinc CC to some compiler not pr
trace
stuff has worked for years. For example, line 17 is
#include "malloc-trace.h"
but there isn't any such file in the respository. (I don't know the svn
incantation to find out if there ever was.)
Depending on what you are trying to do, you might find that
ke sense to spend extra effort on getting
the custom malloc() version to work.
--
Andy Dougherty [EMAIL PROTECTED]
On Sat, 1 Sep 2007, Gabor Szabo wrote:
> It has biten me so let's make sure invalid --gc options are not allowed.
But what if I want to work on --gc=libc? How can I override this?
--
Andy Dougherty [EMAIL PROTECTED]
On Mon, 3 Sep 2007, Gabor Szabo wrote:
> On 9/3/07, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Sat, 1 Sep 2007, Gabor Szabo wrote:
> >
> > > It has biten me so let's make sure invalid --gc options are not allowed.
> >
> > But what if I want
On Fri, 31 Aug 2007, James Keenan via RT wrote:
> On Tue Aug 28 10:00:38 2007, doughera wrote:
> > On Solaris, I'm getting the following failure in both 107-
> > inter_progs.01.t
> > and .02 .t. I suspect it has to do with the use of callbacks in the
> > Solaris
On Mon, 3 Sep 2007, Andy Dougherty wrote:
> On Fri, 31 Aug 2007, James Keenan via RT wrote:
>
> > On Tue Aug 28 10:00:38 2007, doughera wrote:
> > > On Solaris, I'm getting the following failure in both 107-
> > > inter_progs.01.t
> > > and .02
n discussed aplenty, with patches and suggestions and
everything. All that remains is to put the pieces together, but no one
(myself included) has had both the time and inclination to do just that.
See RT #41168.
--
Andy Dougherty [EMAIL PROTECTED]
On Mon, 3 Sep 2007, James Keenan via RT wrote:
> Andy (plus everyone else),
>
> Could you please copy these new versions of
> t/configure/107-inter_progs.0?.t to t/configure/ in your sandbox for
> trunk and try them out?
They appear to pass without complaint.
--
adata.t:
$ egrep '(svn|svk|git): not found' build.log | wc
18
--
Andy Dougherty [EMAIL PROTECTED]
ex, so the
function isn't relevant anymore.
For general purpose use, it's simply inappropriate. It assumes every
function has a -h (or similar) flag. That issue was discussed at length
in
RT#41168: graceful "no compiler" error message?
I'd say just delete it.
--
Andy Dougherty [EMAIL PROTECTED]
Change 21059 removed #include "parrot/parrot.h" from gdbmhash.pmc.
But gdbmhash.pmc then goes on to do all sorts of things with STRING and
PMC. Obviously, they no longer work.
Was this deliberate? If so, what's the plan forward?
--
Andy Dougherty [EMAIL PROTECTED]
On Tue, 28 Aug 2007, James Keenan via RT wrote:
> Andy, I believe I've corrected all the files listed above, plus those
> files in t/postconfigure/ that suffered from the same malady.
>
> Could you please double check?
Yes, it appears you got all those. That just leaves 26
iled on the gdbmhash problem (since fixed).
Testing it today, it passed without problem.
--
Andy Dougherty [EMAIL PROTECTED]
> You've done a lot of work on this in parrot already and I haven't seen
> anything new as far as attributes go for a while. Have you finished
> adding gcc attributes? If so, we can close this ticket.
On attributes, I think so. Warning flags will be a separate projec
http://perlbuzz.com/project-hum/2007/09/first-mod-perl6-handlers.html
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
everyone
use the emulations? That way there's less code to maintain, and everyone
gets to use and test it.
--
Andy Dougherty [EMAIL PROTECTED]
"src/pmc/object.c", line 153: void function cannot return value
>
> I believe this is the same issue as in RT#44009.
>
> It looks like the issue has been fixed.
> Can you confirm that for Solaris 8/SPARC ?
Yes, that one's fixed. I'll close the ticket.
--
Andy Dougherty [EMAIL PROTECTED]
On Wed, 12 Sep 2007, Paul Cochrane via RT wrote:
> On Mon Mar 19 15:59:44 2007, [EMAIL PROTECTED] wrote:
> > On Monday 19 March 2007 12:22, Andy Dougherty wrote:
> >
> > > I found the ticket that introduced this failing behavior, so I'm
> resending
> > >
this at all, but I do note that IPC::Open3
does
untie *STDIN;
untie *STDOUT;
presumably for similar reasons.
--
Andy Dougherty [EMAIL PROTECTED]
901 - 1000 of 1361 matches
Mail list logo
