Steve -- From your private reply to me, we know that ripping out the <<<HERE stuff makes no difference, so it has nothing to do with that. I would also be inclined to rip out all of the bare HTML to make sure you don't have anything funky in there, too, especially since it comes before the error.
...and then [EMAIL PROTECTED] said...
%
% By "comment[ing] out line 11", I take it you mean making a comment of line
% 11. I just did--as this problem woke me from a night's sleep at just past
% 2:30 AM--and the error message is now:
OK; there is obviously some problem with line 11. Since it reads fine
for us and runs when we try it, it must be in your actual code. The next
things I would try are
- if the original file is short, zip it up and attach it, or else make
it available for download, so that we can see the *real* thing
- insert before and after line 11 an innocuous
print "testing\n";
statement, and then break the line around the = so it becomes three
lines and see where the parse error ends up
[Oh, and uncomment the line, of course.]
%
% Parse error: parse error, unexpected $ in [path to file] on line 19
We'll get to that later. Now that we know that there is a problem with
line 11, let's fix it first.
%
% Where will this end?
At the error(s), of course :-)
%
% Steve
HTH & HAND & Happy Holidays
:-D
--
David T-G * There is too much animal courage in
(play) [EMAIL PROTECTED] * society and not sufficient moral courage.
(work) [EMAIL PROTECTED] -- Mary Baker Eddy, "Science and Health"
http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
pgp00000.pgp
Description: PGP signature
