array as “class constant”

[Dormilich]

Hi,

I’d like to have something like

class MyClass
{
    const HASH = array(…);
}

but that’s not allowed, so my question is, should I use a standard or static property instead?

class MyClass
{
    private static $HASH = array(…);
// or
    private $HASH = array(…);
}

[aktar]

I don't know of any other options than to use either a standard or static property

[Dormilich]

and which would you prefer, and why?

[Markus]

Perhaps if you describe your requirement we could offer some advice :)

[Dormilich]

ok (though it won’t make much difference)

initially I wanted a constant (= unchangeable) array in the class, to use it in one of the methods. const HASH = array(…); would have been perfect for that purpose, but it’s not allowed, leaving me with the choice of either using protected $HASH = array(…); or protected static $HASH = array(…);. now I’d like to know, which one would be better.

[dlite922]

serialize your array and put it in a constant :)

Yes that means you can still change it when you unserialize() it. :)

These are the odd cases where PHP does not come up to par with C++.

Use static just so you know you should behave differently while using it, and hopefully to remember to not change it.

Explain your situation a little bit more and I might suggest something else.



Dan

[Dormilich]

serialize your array and put it in a constant :)

very funny, indeed.

I never though such a simple question can get so complicated.

[dlite922]

The way you have it is how I'd do it.

If I was hell-bent on making sure it did not change, I'd make a singleton class and make all the error-codes in there constants and its 2 methods static.

So then I'd use it like this for your deny() function:

if(HTTP_Headers::isValid($code))

header("HTTP/1.1 $code " . HTTP_Headers::get([$code]));

Dan,
[the php nut @]

[Dormilich]

firstly, Abstract Registry is better than Singleton.

secondly, too much computing for that simple purpose.