Parse error

[amsbake]

Please allow me to use this medium to ask..if am inthe right place ..i uploaded a file to my webserver and when i try calling the file from my website it gives me an error like this below what could be the possible problem .

Parse error: parse error, unexpected T_STRING in D:\Domains\beaverbox.net\wwwroot\windowsdoc.php on line 1

 

[beaver6813]

Okay can you paste the top few lines of code from windowsdoc.php so we can help better please

 

[Peter]

es as beaver6813 states post your code that is in windowsdoc.php and we will be able to help, without seeing code it is somewhat difficult to know what you have done. It is strange however that the error is on line 1.

 

[Barrucadu]

It is strange however that the error is on line 1.

I've occasionally cause that error by missing out the '.' when using a variable in the middle of a string. So that is likely to be the cause if it is on line 1.

 

[Peter]

I've occasionally cause that error by missing out the '.' when using a variable in the middle of a string. So that is likely to be the cause if it is on line 1.

But that would cause an error on line 2.

For example the scenario you propose is as follows (although not using a variable):-

<?php
echo "test" "test";
?>

This produces the following error:-

Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting ',' or ';' in PHPDocument1 on line 2

php sees <?PHP as line 1

 

[Barrucadu]

But that would cause an error on line 2.

For example the scenario you propose is as follows (although not using a variable):-

<?php
echo "test" "test";
?>

Not if it was like this, I assume:

<?php echo "test" "test"; ?>

 

[Matthew.]

Edit: Another reason for me to refresh, beaten to it heh.

It's not uncommon for people to just do this:

<?php $this =...

It shouldn't be done, but i've seen it - It would explain the line 1 error anyway.

Perhaps we should just wait for the code

 

[Peter]

Not if it was like this, I assume:

<?php echo "test" "test"; ?>

Just checked and you are right. I was personally expecting it to say it was on line 2 still as php does not tend to care about white space.

Perhaps we should just wait for the code

Perhaps you are right :hehe: was just wondering why an error occured on line 1 and now i know