------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

I have tried to take part of my prov.pl (which worked perfectly) in a inc.pl and add a

require './inc.pl'
[download]

Then it generates me this message :


[Wed Apr 30 16:00:23 2003] [error] Global symbol "$SousMaintenance" re
+quires explicit package name at /var/www/tools/crm/prov.pl line 17.
[download]

So, it is absolutely not a "simple" include.

'require' isn't quite exactly an '#include'. The included file has its own scope which is causing your error. Fortunately, that's not too hard to work around.

Perl has very good support for reusable code. All you have to do is take a little time to figure out how to properly format it. These (along with hmerrill's recommendations]) ought to get you started.

• Coping with Scoping
• Lexical Scoping like a Fox

90% of every Perl application is already written. ⇒

dragonchild

This error is due to the fact that you have strictures in use when including your file which unfortunately does not conply with strict. The 'simple' option is simple to turn off strictures when you're including the file

## effects of 'no strict' limited to the anonymous blocko
{
  no strict;
  require "./inc.pl";
}
[download]

It's a little fiddly I admit, but no more fiddly than a script that doesn't conform to strict (it really does make your life easier).
HTH

_________
broquaint

If you declare $SousMaintenance within prov.pl, like so:

#!/usr/bin/perl
# prov.pl
use strict;
use warnings;
use vars qw( $SousMaintenance );

require './inc.pl';

print $SousMaintenance,"\n";
[download]

with an inc.pl like:

$SousMaintenance = 'value one';
1;
[download]

the problem goes away. Another idea for you is to include a package declaration within inc.pl so that you create a namespace (seperate from main::) like so:

# inc.pl
package myInc;
$SousMaintenance = 'value one';
[download]

Then call it like this within prov.pl:

print $myInc::SousMaintenance,"\n";
[download]


cp
----
"Never be afraid to try something new. Remember, amateurs built the ark. Professionals built the Titanic."

What's wrong with 'use'? I, and probably most of the perl community, develop common code routines all the time - I typically create a perl 'module' - put my common code in there - and then 'use' that module anytime I need access to that code.

If you're not yet familiar with Perl's 'perldocs', get familiar with them. I just did 'perldoc perl', and then searched(using the forward slash '/') for 'module', and here are a few things I found at the top:

           perlmod             Perl modules: how they work
           perlmodlib          Perl modules: how to write and use
           perlmodstyle        Perl modules: how to write modules with
+ style
           perlmodinstall      Perl modules: how to install from CPAN
           perlnewmod          Perl modules: preparing a new module fo
+r distribution
[download]

So, to read the perldocs for 'perlmod', I'd do 'perldoc perlmod'.

I am not exactly speaking of common code, but of common 'text'. This is not a subroutine, it is a common set of declarations and too of code. It is to generate a common look in some HTML pages.

So maybe you want a templating system instead? perrin's templating system comparison is a nice starting point. Personally, I love Template Toolkit II.

Makeshifts last the longest.

Thank you, I have just tried that, but I get the same error
Global symbol "$SousMaintenance" requires explicit package name...

A code snippet would help us to help you debug it :-)