Sounds very strange. Can you do a var_dump() on the sql string?

Can you also test and report back if it works with

  "SELECT * from {$table['users']}"

?

d

Sorry: The error occurs when we define the $query:

$query = "SELECT * from $table[users]"; // => This causes the parse error

echo "Table $table['users']" //=> Parse Error too
echo "Table".$table['users']; //=>OK
$query = "SELECT * from ".$table['users']; //=> OK TOO

It seems we cannot use the correct syntax $table['users'] inside the two ""...

This will work:
$result = mysql_query("SELECT * from ".$table['users']);

This wont work:
$result = mysql_query("SELECT * from $table['users']");

This will, but should send a warning and it isnt:
$result = mysql_query("SELECT * from $table[users]");

The errors happens everywere I call any array with the '' or "" like $table["something"] or $table['something'] inside ""s...

Use the {$array['key']} syntax as I told you.

However, I can't remember if "foo $array['bar']" ever worked or not right now. Someone else?

Hey man WOW, Im impressed, you have already replied!!!

Yes, this solution works:

$query = "SELECT * from {$table['users']}";

But shouldn't "Blah $table['users']" work as well?

Shouldn't PHP at least send a warning when using "$table[users]" even if the other "$arr['foo']" syntaxes where wrong?

Thanks!

Yes, I get you get a NOTICE warning when you use $array[key] (because key will be an undefined constant and therefore evaluate to a string).

Try with error_reporting(E_ALL); before using this syntax.

I did this tests using error_reporting(E_ALL);

Thats my point, the correct array syntax according the doc:
http://www.php.net/manual/en/language.types.array.php
is to call $array['value'] even thought $array[value] will work, but in the later case it should send a NOTICE warning.

well, try this in you system:

error_reporting(E_ALL);
$arr = array( 'foo'  =>  'bar', 'etc' => 'other');

//This will make a Parse Error in PHP 4.1.1:
//echo "Foo value is $arr['foo']";
//This works:
echo "Foo value is ".$arr['foo'];
echo "Foo value is {$arr['foo']}";

//This will work but WON'T send a warning as the doc says:
echo "Foo value is $arr[foo]";
// This will get a parse error
echo "Foo value is $arr['foo']";

Work's right with CVS:

$ php 
<?
error_reporting(E_ALL);
$foo['key'] = 'value';
echo $foo[key];
?>
X-Powered-By: PHP/4.2.0-dev
Content-type: text/html

<br />
<b>Warning</b>:  Use of undefined constant key - assumed 'key' in <b>-</b> on line <b>4</b><br />
-(4) : Warning - Use of undefined constant key - assumed 'key'

Yes, I know your code works, thats not the problem.

Now change your own code:

echo $foo[key];  ==to==> echo "Key value is $foo[key]"; // No warnings!!!!!

And then TRY:
echo "$foo['key']"; // PARSE ERROR!!!

Does it happens with the cvs version?

Ah, I see. No, there's no warning either.

And the Parse Error, do you get it with the cvs ver too?

i'll close this here and create a feature request
for "$array['index']" to be possible or for a better
error message at least ...

see http://bugs.php.net/15677

Ok, but I think it should be seen as a BUG, since we cannot call the array as it should be and we are able to call it as it shouldn't.

PHP is expected work with codes like:
sql_query("SELECT * from $array['table']"); 

and its expected to (but doesnt have to) work with:
sql_query("SELECT * from $array[table]");
and in such case its expected to give a warning...

in both cases the behavior of 4.1.1 is buggy...

Thanks for your time people!
Best Regards

Jo?o Paulo M. Fischer

> PHP is expected work with codes like:
> sql_query("SELECT * from $array['table']"); 

one *could* expect that it understood this,
that's what my feature request is about,
but "PHP is expected" is not right


> and its expected to (but doesnt have to) work with:
> sql_query("SELECT * from $array[table]");
> and in such case its expected to give a warning...

no, this is the current and expected behavior
no warning is generated here as no define() substitution
is done in strings

> in both cases the behavior of 4.1.1 is buggy...
it has been like this ever since 3.0, so you can't
call this 'buggy', call it 'unexpected  behaviour',
'inconsistent design' or whatever, but it is not
a bug ...

> no warning is generated here as no define() substitution
> is done in strings
Why no define() is applied to the string??

From the PHP manual:
[quote]Why is $foo[bar] wrong?[/quote]
[quote]...there must be an expression between the square brackets ('[' and ']').[/quote]

Since there is no expression, the workaround IS to make a define() to the string or integer between the []s and set the value to its own name. 

error_reporting(E_ALL);
define("ke","key");

$foo['key'] = 'aaa';
$foo['ke'] = 'bbb';
echo "<br>It is<br>"
	."Foo[ke] ==> $foo[ke]";
echo "<br><br>It should be:<br>"
	."Foo[ke] ==> ".$foo[ke];

Ok, we can deal with this, but thats not the way it should work according with the good sense and the manual..

Regards

Constants are not looked for within strings, this is why "$foo[key]" does not generate a warning here.  But outside of strings this is a different story.

define ('a','b');
$arr = array('a' => 'apple', 'b' => 'banana');
print $arr['a'];    // apple
print $arr[a];      // banana
print "$arr[a]"     // apple
print "$arr['a']"   // parse error
print "{$arr['a']}" // apple

This bug report is a feature request for "$arr['a']" to print apple.  Regarding print $arr[a] above, if 'a' was not a defined constant, a warning would exist but apple is still printed (if key 'a' exists).