Re^2: Require Carp

The thread referred to is about the dynamic loading, it usefulness, and attempted optimizations. I know I use Carp; it is needed for the compile.

But what I did find (looking at code examples) is that "requiring warnings" prior solved the problem.

Tis strange that Carp doesn't complain when a dependency is not present.

Comment on Re^2: Require Carp - doesn't

Replies are listed 'Best First'.
Re^3: Require Carp - doesn't by chromatic (Archbishop) on Dec 07, 2006 at 19:25 UTC
This has nothing to do with Carp's dependencies (and it doesn't depend on warnings). In fact, your "fix" is actually incorrect and buggy and Steve Peters posted his comment to warn people away from doing that! It has nothing to do with dynamic loading either. It has everything to do with subroutine prototypes, as Steve explained. Perl hasn't loaded Carp when it tries to compile the `carp()` calls. Without parentheses, it has no idea how many arguments the function should take (or even if `carp` is a function call at all), so it warns. It would do that even if you weren't trying to use `perlcc` or Carp.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Require Carp - doesn't
by chromatic (Archbishop) on Dec 07, 2006 at 19:25 UTC

This has nothing to do with Carp's dependencies (and it doesn't depend on warnings). In fact, your "fix" is actually incorrect and buggy and Steve Peters posted his comment to warn people away from doing that! It has nothing to do with dynamic loading either. It has everything to do with subroutine prototypes, as Steve explained.

Perl hasn't loaded Carp when it tries to compile the carp() calls. Without parentheses, it has no idea how many arguments the function should take (or even if carp is a function call at all), so it warns.

It would do that even if you weren't trying to use perlcc or Carp.

[reply]
[d/l]
[select]