gubed-devel

[gbd-dev] Gubed & PHP5 private, protected and public keyword problem

[Uros D. <du...@lu...>]

Hi all!
First, thank you for nice debugger!
I installed it yesterday (SuSE 10, Quanta 3.4.2, Gubed from 
GubedQuanta3_4.tar.gz package and PHP Version 5.0.4) and I have found a 
following problem...

Debugger works good until it reaches code like this:

class TAuthenticate
{
	public $FDBDSN;
	public $FDBTableName;
	public $FDBIDField;
	...
}

and says 
Gubed: Syntax or parse error in ....

I have found that keywords:
public, protected, private (introduced first in PHP5)
are not recognised as valid commands.
When I comment them
//	public $FDBDSN;
//	public $FDBTableName;
//	public $FDBIDField;

No syntax error is thrown from Gubed

Is there a way to tell Gubed that these keywords are valid while it parses a 
file and checks a syntax?

Thank you in advance!

-- 
Dukanac Uros

=== Fortune =====
Aleph-null bottles of beer on the wall,
Aleph-null bottles of beer,
	You take one down, and pass it around,
Aleph-null bottles of beer on the wall.

Re: [gbd-dev] Gubed & PHP5 private, protected and public keyword problem

[Linus M. <Li...@mc...>]

Hi!

The next version of Gubed supports PHP5 syntax better. Please try:
http://x.mccabe.nu/public/Gubed/0.3.3

I think the 3.5 package works with quanta 3.4, but it was so long ago, i dont 
remember...

upgradeing to quanta 3.5 might be a good idea anyway..

cheers

/linus

On Monday 12 June 2006 14:23, Uros Dukanac wrote:
> Hi all!
> First, thank you for nice debugger!
> I installed it yesterday (SuSE 10, Quanta 3.4.2, Gubed from
> GubedQuanta3_4.tar.gz package and PHP Version 5.0.4) and I have found a
> following problem...
>
> Debugger works good until it reaches code like this:
>
> class TAuthenticate
> {
> 	public $FDBDSN;
> 	public $FDBTableName;
> 	public $FDBIDField;
> 	...
> }
>
> and says
> Gubed: Syntax or parse error in ....
>
> I have found that keywords:
> public, protected, private (introduced first in PHP5)
> are not recognised as valid commands.
> When I comment them
> //	public $FDBDSN;
> //	public $FDBTableName;
> //	public $FDBIDField;
>
> No syntax error is thrown from Gubed
>
> Is there a way to tell Gubed that these keywords are valid while it parses
> a file and checks a syntax?
>
> Thank you in advance!