Unexpected $ what does it mean

[moldboy 0]

You see I have a most intresting problem, basicaly I get the following error:

Parse error: parse error, unexpected $ in /path/result.php on line 99

Now normaly when I have problems I go to line 99 and add a ; or a " or something the problem is in my file line 99 is </html>,

 <tr bgcolor="#FFFFFF">    <td width="25" height="5" background="images/q3.png"> </td>    <td height="25" align="right" valign="top" background="images/bot.png"><span class="style2"><a href="help.htm">Help</a></span></td>    <td width="25" height="25" background="images/q4.png"> </td>  </tr></table><br><span class="style3">a d-gression service</span></body></html>

Infact the php ended about 20 lines ago on line 79

?>

Any idea, I can't figure out what the problem might be.

[Daehawk 0]

Your problem is that you missed either a } or a ; in one of your previous lines. Find what you edited and look there. I get this now and then and I just check what I did. If you use Word Pad....or something like that...I'm sorry....get Matrix Y2k Website Studios, works wonders on telling you which { is lined up with which }.

[moldboy 0]

Thanks I had a foreach loop inside a while loop and didn't end one of them.

[Daehawk 0]

Thanks I had a foreach loop inside a while loop and didn't end one of them.

158994[/snapback]

 

No problem, yeah that's one thing you always have to do is check if you have ended everything.

[moldboy 0]

That and finish every line with ;, you know that is my least favorite thing about PHP. Everytime I forget it. What's even worse is that the error, unexpected something expected , or ;, well if you expected it, then put it there!

[Daehawk 0]

That and finish every line with ;, you know that is my least favorite thing about PHP.  Everytime I forget it.  What's even worse is that the error, unexpected something expected , or ;, well if you expected it, then put it there!

159048[/snapback]

LoL yeah, I know...I got used to it now though, and it doesn't have to be every line cause some lines you don't need them at the end. like the ones that start if (blah = blah) { and stuff like that LoL.....You get used to it over time.

[hype 0]

That's what I hate about php, I always miss it out, and mess out my entire code, and wasted my whole day of coding time... I hope there's a machine tat would point out all wrong codes and fixed them automatically for you..

[beeseven 0]

That and finish every line with ;, you know that is my least favorite thing about PHP.  Everytime I forget it.  What's even worse is that the error, unexpected something expected , or ;, well if you expected it, then put it there!

159048[/snapback]

Too bad most programming languages require you to finish commands with a semicolon

[moldboy 0]

You know it knows when we are on a new line as it returns the line number that the error is on, yet it can't deduce that we ment to end the line, but then again when you do someting like:

while(something = somethingelse){$whole bunch of stuff here;bunch more stuff}

the first bunch of stuff could technicaly follow the { and I know most people don't do that, and if it assumed each line break was ; then it would return new errors!

[Daehawk 0]

You know it knows when we are on a new line as it returns the line number that the error is on, yet it can't deduce that we ment to end the line, but then again when you do someting like:

while(something = somethingelse){$whole bunch of stuff here;bunch more stuff}

the first bunch of stuff could technicaly follow the { and I know most people don't do that, and if it assumed each line break was ; then it would return new errors!

159427[/snapback]

I always hit enter after the {'s and ;'s keeps everything organized so it's alot easier to read and you can tell where an error could be earlier...like if you had something wrong with the while statement and you had something else there as well...you might change the wrong thing and create a different error and just get more confused LoL.