What are 'CONSTANT1' and 'CONSTANT2'? In your sample code these two bare words are the things that generate 'Bareword "CONSTANT2" not allowed while "strict subs" in use' type errors. No trivial variations on the code you provide give the error you report, at least with Perl 5.10.1.

I have read that perl used to allow pkg'$var and this is still supported

"'" is allowed as an alternate to "::", so $pkg::var could be (very unwisely) written as $pkg'var. Writing pkg'$var could definitely result in the error you get. But I don't see that in the code, so why do you bring it up?

The hashed codes are japanese characters.

No, there are no Japanese characters in the iso-8859-1 character set. You are not giving Japanese characters to perl. Perhaps you meant to include "use utf8;" to indicate your source is encoded using UTF-8 rather than iso-8859-1?

I tried using the "use utf8;" line and it created a recursion error. As mentioned above I am using EPiC for eclipse and have the pages encoded to UTF-8 through the interface. Also the output to the HTML pages that the script is creating is handling the characters fine.

If you still think that it is a UTF-8 error, I am assuming I would need to copy all of my code out to say notepad, use the UTF-8 line, and then paste back in. If there is an easier way would be happy to hear as it will save me a few files of code to not do this for.

As for the $pkg'var comment, I just wanted to ensure readers that I was aware of this and that this wasn't the cause.

Works for me on *nix on everything form 5.6 to 5.12 with no errors (after putting something in for the CONSTANT's). Any change you've got some weird unprintable character in it somehow? What are you using for an editor?

The various forms of multiple quoting you have wouldn't work, except the one using a plain doublequote ". That should work, but single quote is also fine. The issue with single quotes acting like package names is when they look like part of the variable; e.g., if you had $x = "$users's coat".

This is the closest to a solution of the replies so far, I am using Eclipse with EPIC package installed. When I save the file the previously mentioned error appears.

#!c:\Perl\bin\perl
use warnings;
use strict;
use CGI ':standard';
use constant CONSTANT1 => '../perlscript1.pl';
use constant CONSTANT2 => '../perlscript2.pl';
my $htmlPage = CGI->new;

print $htmlPage->a( { -href => CONSTANT2
                    , -target => '_self' }, 'こちら'
+ );
print "</p>\n<p>";
print $htmlPage->a( { -href => CONSTANT1
                    , -target => '_self' }, '&#21033;&#29992;&#35215;&
+#32004;' );
print "</p>";
[download]

Care to post a piece of code that actually acts like you describe it?

The code I posted in response to fullermd has a sample of the code that comes up with the error.

To restate my problem, the code compiles and runs on the system I am testing it on, but in the eclipse EPIC environment it marks the specific line with a bad name error. I just thought to test the script from the command line and it works fine with no error calls.

I would like to know or be given direction as to why this is occuring to learn more about the proper way to code with perl.

Well, it looks like perl to me any all the perl's on my system, and it sounds like it's working fine for you with perl. So I'd say you're coding perl properly.

So it sounds like you really have an EPIC problem; maybe it has a bug in its parsing somehow. 's beyond me; I've never used anything Eclipse-ish. I don't know what support channels exist there, but you could see if someone there knows what's up.

You could also try fiddling the code around a bit and see if you can find something that's making it's confused. Perhaps it doesn't like the commas at beginning of line? Try changing something like

print $htmlPage->a( { -href => CONSTANT2
                    , -target => '_self' }, 'こちら'
+ );
[download]

to

print $htmlPage->a( { -href => CONSTANT2,
                    -target => '_self' }, 'こちら' )
+;
[download]

instead (comma moved to the end of the first line rather than start of the second). Or put it all together on one line. Eliminate the -href, and try with just the -target, and vice versa.