Alberto Simões (a...@alfarrabio.di.uminho.pt)

Well, manual installation worked.
Please ignore :)

Alberto

I'll try again.
By the way, this was under Mac OS X (Tiger).

Alberto

Hi

I was trying to compile libwww under Perl 5.10, and I got:

Running make test
/opt/local/bin/perl t/TEST 0
base/common-req.........ok
[...]
local/get...............ok
local/http-get..........ok
local/http..............HTTP Server terminated
local/http..............1/18 Can't call method "is_redirect" on an
undefined value at local/http.t line 196, <DAEMON> line 1.
local/http.............. Dubious, test returned 22 (wstat 5632, 0x1600)
  Failed 18/18 subtests
local/protosub..........ok

Anybody knows if this is specific of perl 5.10, or if I should complain?

Also, it is strange that the module name is
  GAAS/libwww-perl-5.808.tar.gz
is libwww following perl 5 version number?

Cheers
ambs

I am missing a direct URL for somewhere :D

ftp.cpan doesn't have it yet.

Cheers and congratulations for the good work
ambs

Thanks for the hint. I'll do that.

Cheers
ambs

Good guess.
It would be nice to check that. (I'm sleepy).

   "Summary of my perl5 (5.0 patchlevel 5 subversion 5) configuration:"

And yes, they are all the same (same tester).

Is this perl 5.5? :-S

Cheers
ambs

Hi

I received a bunch of failed tests for my CPAN modules, and one of the
errors is:

Use of reserved word "our" is deprecated


Since when, and how, is "our" deprecated? :-S

TIA
ambs

After sending my email I found out that this is normal. as somebody on
#perl told me, "use strings when you need to manage money".

Thanks
ALberto

Hi

I was trying on my PowerBook G4:

my $x = 1000.01 - 1000;
print $x;

it prints
0.00999999999999091


Now the question is:
the solution is to use BigNumber module?

Cheers
ambs

I hope so. I think we should.

Hi

In the other day I noticed that if my code uses $' or $` somewhere (for
instance, in a function I never call), all regular expressions on my
code get a LOT slower. This is specially true if I am matching against
big strings.

Ok, I understand a little why this happens. Basically, the regexp engine
will save the context for each match it does.

The question is, can't we make this lexical? I mean, if $' and $` are
used inside a sub, just change the way regular expressions work on that
sub? I understand that might arise some other problems, but here are my
ideas just to make you all think a little on it :)

Cheers
Alberto

Erm, ok, not properly what you mean.

void foo ()
  {
  }

  int bar ()
  {
    return foo();
  }

  main(void) {
    printf("%d\n",bar());
  }

compiling gcc -Wall

foo.c: In function 'bar':
foo.c:7: error: void value not ignored as it ought to be
foo.c:8: warning: control reaches end of non-void function
foo.c: At top level:
foo.c:10: warning: return type defaults to 'int'
foo.c: In function 'main':
foo.c:11: warning: implicit declaration of function 'printf'
foo.c:11: warning: incompatible implicit declaration of built-in
function 'printf'
foo.c:12: warning: control reaches end of non-void function


Not *too* bad :)

foo.c:11: error: invalid use of void expression

where

foo.c:11 --    printf("%d\n",bar());

gcc 4.1.x

Cheers

Just found all this thread on my Junk folder. Why in hell use so many
'$$$' on the subject line? :-)

I know, I am adding entropy, but I couldn't resist.
Alberto