ork? That'll give us
something more definite to base it on.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Ian Langworth has created a great quickref for Test::* modules at
http://langworth.com/downloads/perl_test_refcard.pdf. I put a link to
it up on qa.perl.org.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Wed, May 05, 2004 at 11:40:32PM -0200, Gabor Szabo ([EMAIL PROTECTED]) wrote:
> Is there some command line tool that can be used to report bugs to RT ?
Sure, it's called "sendmail".
If you want to send a bug on Test::Harness, send an email to
[EMAIL PROTECTED]
xoa
--
And
hors ignore it, I'm sure.
I have a note in my modules saying "Please send all requests to".
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
);
my $sql2 = 'select size from . where name = "LITERAL: \r\n"';
my $sql3 = "select size from . where name = \"EXPANDED: \r\n\"";
@@ -97,10 +93,12 @@
# do a little work
foreach (1,2,3) {
my $sth2 = $dbh->prepare($sql2);
+ isa_ok( $sth2, 'DBI::st' );
$sth2->execute();
$sth2->fetchrow_hashref;
$sth2->finish;
my $sth3 = $dbh->prepare($sql3);
+ isa_ok( $sth3, 'DBI::st' );
$sth3->execute();
$sth3->fetchrow_hashref;
$sth3->finish;
@@ -109,7 +107,7 @@
# load dbi.prof
$prof = DBI::ProfileData->new();
-ok($prof and ref $prof eq 'DBI::ProfileData');
+isa_ok( $prof, 'DBI::ProfileData' );
# make sure the keys didn't get garbled
$Data = $prof->Data;
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ike() because we need $1
# version matches VERSION? (DBI::ProfileDumper uses $self->VERSION so
# it's a stringified version object that looks like N.N.N)
-ok($1, DBI::ProfileDumper->VERSION);
+is( $1, DBI::ProfileDumper->VERSION, 'Version numbers match' );
# check that expected key is there
-ok($prof =~ /\+\s+1\s+\Q$sql\E/m);
+like( $prof, qr/\+\s+1\s+\Q$sql\E/m );
# unlink("dbi.prof"); # now done by 'make clean'
-
-1;
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Changes file that tells me otherwise.
The most "very recent" version of Test::More is from August 2002.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
it comes from a DB,
should be taint-aware, I think.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
an only incorporate tests when everything is
covered." ANY amount of test improvement is still an improvement. I
sent some DBI test patches a month ago, and I thought Tim Bunce was
going to reach through the monitor and give me a big wet kiss.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
aying) projects came to the fore.
Let's understand the problem before proposing solutions.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
sing coverage, especially prior to DBI v2.
Did I not hit all the existing test files? Or just some of 'em?
Also, look into using Devel::Cover to see which parts of DBI are getting
exercised and which aren't.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
at at one point, Jesse Vincent was having problems with RT,
and was moving, and got hacked, all within about a week of each other
or so, so syncing with CPAN didn't happen. Something like that.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
ring and then it was happy.
YMMV.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
42), so I
> think maybe this is a different problem.
One easy, empirical way to find out!
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
inal line there should be a simple "return $ok".
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
tooltip" thing isn't portable, though.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
So I'm giving an LT on Phalanx next week in Buffalo. Anything in
particular y'all think I should mention?
xoxo,
Andy
To: Andy Lester <[EMAIL PROTECTED]>
Subject: Your Lightning Talk
Your proposal for a Lightning Talk at the 2004 YAPC::America::North has been accepted.
g a module to do, and
then working on it, which has so far not worked at all, that we should
hold up a module (or a handful of them) and say "OK, this is what we're
working on". It certainly seemed to work with the DBI stuff last month.
Thoughts?
xoa
--
Andy Lester => [EM
; them out in my build script.
Seems to me that if T:H is passed a test file, it's not unreasonable for
it to expect at least one test.
How about if T:I created a dummy test in the absence of any others?
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
modules.
I agree about skipping noise, but then you'd have T::H ignoring empty
files, which might, in another case, indicate something gravely wrong.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Fri, Jun 18, 2004 at 12:03:51PM -0700, chromatic ([EMAIL PROTECTED]) wrote:
> Is anyone else interested in writing some small excercises for people to
> practice their Perl test-fu?
Yes. A lot. I think it'll bring many to the light.
xox,
Andy
--
Andy Lester => [E
= My::Foo->new( bar => 14, bat => \$wango );
isa_ok( $foo, 'My::Foo' );
The more checks you have, the better. Sure, the first isa_ok
technically "covers" the constructor, but why not check after EVERY
constructor? The 2nd example is really an entirely different test
n your ASP.Net
side? A 500 error is a problem on the server. That error is logged
somewhere on the server.
This isn't a Mech problem.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
what Phalanx is about. I think
Parse::RecDescent is on the Phalanx 100.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
eful *heuristic* for test effectiveness. Like all
> heuristics if you push it too far it falls apart. Get as close to 100% as
> is useful and don't worry about the rest.
Words to live by.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
meant to be
> configured in the "use" statement, and have little or no subroutines
Devel::Cov er handles this for you.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
mes. Even though
This also ignores the constants that we usually make all-caps.
use constant PANTS => 42; # is actually sub PANTS() {42}
I'm not sure if that's a feature or a problem.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
s to tests?" "Yeah!" "OK, here you go" "Thanks,
released!"
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
at would be the most swell.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
anx.kwiki.org, too, when we were together at OSCON.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
w this will do.
Thoughts?
xoa
- Forwarded message from PAUSE <[EMAIL PROTECTED]> -
The uploaded file
Test-Regex-0.01.tar.gz
has entered CPAN as
file: $CPAN/authors/id/P/PE/PETDANCE/Test-Regex-0.01.tar.gz
size: 2890 bytes
md5: 565b7e75907b621dfc411bb967b38fe7
No act
if someone generated Devel::Cover dumps for the
Phalanx 100. Like http://pjcj.sytes.net/cpancover/ but for
http://qa.perl.org/phalanx/distros.html.
I also wonder if the 100 would be different now than when I created it a
year ago.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
from pair.com and from cpan.org. If anyone else has FTP logs they can
submit to me, I'd love to have 'em.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
$ host cpan.org
cpan.org has address 66.39.76.93
$ host cpan.pair.com
cpan.pair.com has address 66.39.76.93
Last year, I got different logs from Graham and Pair. Any other
suggestions since they're apparently the same now? Mirror-owners I
should talk to?
xoa
--
Andy Lester =>
_ok( $diff, '>=', 2, 'Actual time diff is at least 2 seconds' );
+cmp_ok( $diff, '<=', 10, '... and no more than 10' );
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
quot;tr-amper", "&tr() is func" );
# y operator
can_ok( 'main', "y" );
eval "y('unqualified')";
like( $@, qr/^Transliteration replacement not terminated/, "y('unqualified') doesn't
work" );
is( main::y('main'), "y-main", "main::y() is func" );
is( &y('amper'), "y-amper", "&y() is func" );
=pod
from irc://irc.perl.org/p5p 8/12/2004
kane-xs bug or feature?
purlYou decide
kane-xs [EMAIL PROTECTED] ~]$ perlc -le'sub y{1};y(1)'
kane-xs Transliteration replacement not terminated at -e line 1.
Nicholasbug I think
kane-xs i'll perlbug
rgs feature
kane-xs smiles at rgs
kane-xs done
rgs will be closed at not a bug,
rgs like the previous reports of this one
Nicholasfeature being first class and second class keywords?
rgs you have similar ones with q, qq, qr, qx, tr, s and m
rgs one could say 1st class keywords, yes
rgs and I forgot qw
kane-xs hmm silly...
Nicholasit's acutally operators, isn't it?
Nicholasas in you can't call a subroutine with the same name as an
operator unless you have the & ?
kane-xs or fqpn (fully qualified package name)
kane-xs main::y() works just fine
kane-xs as does &y; but not y()
AndyIf that's a feature, then let's write a test that it continues
to work like that.
=cut
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
A link from Ask Bjoern Hansen's blog: http://www.askbjoernhansen.com/
"How To Misuse Code Coverage"
http://testing.com/writings/coverage.pdf
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Fri, Aug 13, 2004 at 02:29:40PM +0200, Rafael Garcia-Suarez ([EMAIL PROTECTED])
wrote:
> Andy Lester wrote:
> > #./perl -T
> ^^
> the lack of "!" here gave me a small headache during the integration.
Sorry about that. Here's one teeny more patch to add, to mi
On Tue, Aug 17, 2004 at 09:50:11AM +0200, Rafael Garcia-Suarez ([EMAIL PROTECTED])
wrote:
> BTW, isn't the habit to post to c.l.p.announce a bit deprecated now ?
Yeah, now we just post to use.perl.org.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
don't have to do it,
I'd appreciate it, since I have too many things in the hopper right now,
but I'd really like to get it announced.
Thanks,
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
et the patches to Sean Burke, and he'll work
with the team. If it's a core module like CGI.pm, then you have to work
with Lincoln and/or p5p.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
nfomation as possible (including the test name).
I can't see changing it. What if there are 1000 failed tests?
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Oct 16, 2004, at 8:02 PM, Mark Stosberg wrote:
How can I write an automate test for a shell command that prompts for
output. I first tried just using backticks, but that hangs waiting for
input.
Will it take its input from STDIN? If so, pipe stdin to it.
xox,o
Andy
--
Andy Lester => [EM
ne of my modules fails to make a PPD. If
they mailed me to tell me, I'd love it.
Let's not go about this in a vacuum, where we think we have to harvest.
Take the time to work WITH ActiveState.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ame will give you the path. This is very handy for
doing things like:
vim `perldoc -l Module::Name`
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
oplites care to chime in on status?
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
be 4 hours. Oh, and we need E for support, and F to modify
infrastructure. 4 hours each." That's 6 tasks at 4 hours each.
You're now at 24 hours. You haven't even started work and you're 20%
over the original estimate. :)
Works fairly well for us, and by "fairly well&quo
Also I was thinking it would be nice to be able to run prove and
Devel::Cover together by possibly adding a -M to prove
prove -MDevel::Cover -Ilib -v t/*
I don't recall this -M/-m suggestion, but I like it.
Can someone please submit it to the CPAN queue?
Thanks,
xoxo,
Andy
--
Andy L
tp://qa.perl.org/phalanx/.
If you'd like to help out, join the perl-qa mailing list, or email
me at [EMAIL PROTECTED] I look forward to hearing from you.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
dded as we go along.
Jay Flowers has started working on CGI::Application, I believe. Jay,
I'll need to know the Before stats on it.
The CMS on perl.org makes updates really simple, so please let me know
what's going on and I'll updated fairly often.
Thanks,
xoxo,
Andy
--
Andy L
We now have 5 distributions currently being worked on in the Phalanx
project. See http://qa.perl.org/phalanx/status.html for details.
Come join the fun! Pick a module and let me know about it!
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
an arg for unlink and not for ok.
Thanks. I rewrote it as
is( unlink($filename), 1, "Remove $filename" );
Better to test for exactness than truth.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
lease include me on those, as I'm updating Test::Reporter as my
module on Phalanx.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
orter, but I haven't done anything yet, other than suck it
into my CVS.
How are the rest of you doing?
Thanks,
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I'm going to be adding to
Test::Harness soon (Where are those tuits?) is the ability to run the .t
files in random order, in the hopes of exciting bugs that are for some
reason dependent on order of execution.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
hat order. The rest are
shuffled. But nothing definite yet.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
> Is it worth trying to agree on a de facto standard name for
> such a beast: 99-pod.t/99_pod.t/99.pod.t/99pod.t?
Personally, I'd just as soon not have it be one of the numeric ones. It
doesn't matter what order it's run in.
xoa
--
Andy Lester => [EMAIL PROTEC
7;re holding off on the biggies (the modules in
the top two sections of the list) until we've had some success with the
other 70. I definitely want all 30 of the top 30 covered.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ml until we get some successes on
smaller modules, and some lessons learned from them.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
irely. When I came back from OSCON I was awed by how much
raw Perl power is in London.pm, and how much they drive the Perl
community, especially on Perl 6. I came back to Chicago.pm and
challenged them to do something similar with Phalanx.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://qa.perl.org/phalanx/status/Archive-Tar.pod and mail it back to
me, that would be fine.
Thanks,
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
I got no response from the author. In worst case, I plan to post the
tests files on rt.cpan.org.
I'm sure Damian will be fine with it. I told him about the project a
while ago and he seemed genuinely excited about it.
xoa
-
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdanc
Anything that uses the C operator is a prime candidate for
bugginess. Please keep an eye out for them as you do your testing.
Any function that contains C oughta be heavily checked.
Ditto anything that uses C or C without a sort.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http
/ # -v =verbose, -b=use blib, -r=-recursive
Many fun things to do, geared towards making the cycle of code/test a
shorter one...
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
prove
and Test::Harness.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
ally, I find the POD useful when I'm going thru a Devel::Cover
run. I interleave POD with functions and I like to refer to my docs.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
tc );
while ( my($key,$val) = each %tests ) {
# do a test
}
The order in which these tests are done will be different between runs
of the code...
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
ind a
clean way to make it an option, I'll do so.
If I've got docs for a function, then I want to see them while I'm
considering the code. Code and documentation are, especially w/POD,
interconnected. That's the beautiful thing about POD.
--
Andy Lester
[EMAIL PROT
How am I going to test this ?
Take a look at Test::Warn for warnings, and Test::Exception for errors.
I think qa.perl.org needs a listing of Test::* modules so that people
know what's available.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.per
ght now. Actually,
he's done working, but I have to finish my part.
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
prove begins with #!/usr/bin/perl and prove-switches.t
runs it with
my @actual = qx/$prove -Ifirst -D -I second -Ithird -Tvdb/;
A $^X should be inserted here.
(in bleadperl, the shebang line of prove is fixed when installed.)
What should be in prove's shebang?
xoa
--
Andy Lester
[
there? Or are you saying I should run it as
my @actual = qx/$Config{startperl} $prove -Ifirst /;
xoa
--
Andy Lester
[EMAIL PROTECTED], AIM:petdance
http://petdance.com/ http://use.perl.org/~petdance/
> It appears that this doesnt error on 5.8.2, but is repeatable on 5.00503,
> as follows:
I don't see any problem here. You can't have more than one plan.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
the name itself, and all of my Test::* modules create their own test
name if there's not one passed.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
;t use numbers for your test
>names.
> # Very confusing.
ok() is not a comparison. is() is a comparison.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
going to define arbitrary rules based on a sample size of one.
I DO want to document the format, however, so that other languages can
write to the T::H format reliably, and let T::H become the uber-tester.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
n this, unless I'm missing something.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
> I've had more time recently, so I smoke tested the Phalanx 100.
So what did you discover?
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I'd like to put some kind of reasonably fresh content up on qa.perl.org.
If anyone's got, say, module announcements, that would make sense to
appear on qa.perl.org, please send 'em to me. I'd just like qa.p.o to
be more than a pile of links.
thanks,
xoa
--
Andy Lester
> Because it is, in Test::More. I've yet to need it. Nobody's given me a
> patch to implement it.
And T::H doesn't recognize anything like that either?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
It's been a while since I've heard from any hoplites. Where are you on
your individual Phalanx modules?
I know Hoplite Gessner is pretty close to done on his, but I haven't
heard back on whether his changes were accepted.
xoxo,
Commander Andy
--
Andy Lester =>
> Probably the most important change is that Devel::Cover will now work
> with programs that turn on tainting. I gather this is important for
> Phalanx. Hi Andy!
Never mind Phalanx, I'd just like to run Test::Harness under it!
I'll let you know what I find!
--
Andy Lester
Thanks for the updates!
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
portability wins.
Agreed, but can we get a verification on that first? I've never had
any problems with it on Perl 5. Are we targeting some even-weirder-
than-Perl-5-runs-on compilers or something?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ts.c
PMC *pio = buf.ev-
>u.io_event.pio;
int fd = PIO_getfd(NULL, pio);
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
const
char* const p;
The pointer "p" is considered const, but the bytes it points at
are not
They can be combined:
const char* const p;
Both constant pointer and constant data
The rule is that const affects the thing immediately following it.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
'm all over the portability, c.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ler knows that buffer can't be getting initialized.
Think of consting your function parameters as a very basic contract
with the caller.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
T_NULL(x) x = 0
# define SET_NULL_P(x, s) x = (s)NULL
And for that matter, what's wrong with just using x = NULL
everywhere? Why do we need a macro to do this?
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
ler knows that buffer can't be getting initialized.
Think of consting your function parameters as a very basic contract
with the caller.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
;re NOT using those
macros and not getting problems.
I'm gonna yank 'em.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
interp->lo_var_ptr like we think we are. SET_NULL is relaly
SET_NULL_OR_SO_YOU_THINK_HA_HA_HA.
Now I'm DEFINITELY rmeoving it.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Run "make headerizer"
The .h file should now have PARROT_API for the function in question.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Anyone out there using the Intel compiler?
How are you running Configure.pl?
Thanks,
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
: ignoring option '-W'; no argument
required
icc: error #10149: option '-cxxlib-gcc' not supported with the
current installed GCC
make: *** [src/ops/core_ops.o] Error 1
What is icc looking for in gcc that I don't have?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
I'm very uncomfortable with removing #pragma once from our header
files. It is perfectly valid C89 code, and I think bowing to a
broken compiler is unhealthy precedent.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
valid C89, will not compile parrot, and
upgrading to a version with the proper patch is required.
It shouldn't be too tough to drop a #pragma once in the sample
program that Configure.pl uses to check validity of the compiler, no?
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Jun 12, 2007, at 1:39 PM, Allison Randal wrote:
Do we have any proof that it does speed up compilation with msvc?
Littering our code with "optimizations" for odd compilers is also
an unhealthy precedent.
Darn you and your pragmatism!
DO we indeed have proof of a speedup?
xo
pragma, and we cannot
rely on it.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
or not, but if I do it's
going to be primarily for the hackathon...
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
201 - 300 of 498 matches
Mail list logo