[SOLVED] Parse error: syntax error, unexpected T_STRING ....

[nathanmaxsonadil]

What's wrong with this if statment?

if (function_exists('realpath') AND @realpath(dirname(__FILE__)) !== FALSE)
{
$system_folder = str_replace("", "/", realpath(dirname(__FILE__))).'/classes/';
}

It gives me this error

Parse error: syntax error, unexpected T_STRING in my_dir/install.php on line 8

[Orio]

You didn't close the brackets of the str_replace.

Sorry my bad- its not the problem

 

Orio.

[nathanmaxsonadil]

I dont understand what you mean

Can you show me how to fix the  code?

[lemmin]

Are you sure? It looks to me like he did. I would think that "__FILE__" is the problem. Is that defined somewhere? Can you define something to start wtih an underscore? try changing that.

[trq]

The line number php reports an error on is not always the precise line. I don't see any errors there, can we maybe see a few more previous lines.

[Orio]

<nvm my mistake!!>

 

Orio.

 

@lemmin that is a predefined constant. Check this.

[trq]

would think that "__FILE__" is the problem. Is that defined somewhere? Can you define something to start wtih an underscore? try changing that.

 

__FILE__ is a built in constant.

[lemmin]

Whoa cool, thanks Orio, I learn something new here everyday!

[nathanmaxsonadil]

ok here's my code from line 1 to 11

1 <?php
2 ob_start(); 
3 session_start(); 
4 $dbuser = 'my_user'; 
5 $dbpass = 'mypass'; 
6 $dbhost = 'localhost'; 
7 $db = 'my_db; 
8 if (function_exists('realpath') AND @realpath(dirname(__FILE__)) !== FALSE)
9 {
10 $system_folder = str_replace("", "/", realpath(dirname(__FILE__))).'/classes/';
11 }

P.S: sorry for not replying back soon I was reading something else

[nathanmaxsonadil]

lol I forgot to put a end ' on line 7

[akitchin]

you're missing a closing single quote on the line before it.. honestly, a little bit of syntax highlighting or even two minutes of hard searching could have shown that.

 

EDIT:  you beat me to it.  seriously, spend a little bit of time trying to find the error on your own before defaulting to us to find the parse error.  parse errors should be fairly easy to resolve, since they're usually a symptom of some careless or inattentive programming.

[Daniel0]

EDIT:  you beat me to it.  seriously, spend a little bit of time trying to find the error on your own before defaulting to us to find the parse error.  parse errors should be fairly easy to resolve, since they're usually a symptom of some careless or inattentive programming.

 

Syntax highlighting would also point a such error out quite easily.

[nathanmaxsonadil]

I looked at it but  I guess I missed it

when I looked at my post i saw what was the problem