Re: [PHP] How to store data that doesn't change?

2010-09-16 Thread tedd

At 8:46 AM -0400 9/15/10, Peter van der Does wrote:

Hi,

How do you people store data that doesn't change, an example of this
would be the version number of your software. You might want to use it
through out your program but how to you store it?

As far as I can see there are several options to use this data.
1. Global Variable
2. Store it in a registry class
3. Store it in a named constant.
4. Use a function that will return the data (kind of like a regsitry
class but it's not a class)

Personally I don't like option 1 but what about the other options. Is
any of them faster then the others. What other pros and cons are there.


Make it's a Constant -- it's simply a Global that doesn't change.

I typically hold such things in a global configuration file that can 
be included when needed.


Cheers,

tedd

--
---
http://sperling.com/

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[PHP] How to store data that doesn't change?

2010-09-15 Thread Peter van der Does
Hi,

How do you people store data that doesn't change, an example of this
would be the version number of your software. You might want to use it
through out your program but how to you store it?

As far as I can see there are several options to use this data.
1. Global Variable
2. Store it in a registry class
3. Store it in a named constant.
4. Use a function that will return the data (kind of like a regsitry
class but it's not a class)

Personally I don't like option 1 but what about the other options. Is
any of them faster then the others. What other pros and cons are there.

-- 
Peter van der Does

GPG key: E77E8E98

IRC: Ganseki on irc.freenode.net
Twitter: @petervanderdoes

WordPress Plugin Developer
Blog: http://blog.avirtualhome.com
Forums: http://forums.avirtualhome.com
Twitter: @avhsoftware

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] How to store data that doesn't change?

2010-09-15 Thread Peter Lind
On 15 September 2010 14:46, Peter van der Does pvanderd...@gmail.com wrote:
 Hi,

 How do you people store data that doesn't change, an example of this
 would be the version number of your software. You might want to use it
 through out your program but how to you store it?

 As far as I can see there are several options to use this data.
 1. Global Variable
 2. Store it in a registry class
 3. Store it in a named constant.
 4. Use a function that will return the data (kind of like a regsitry
 class but it's not a class)

 Personally I don't like option 1 but what about the other options. Is
 any of them faster then the others. What other pros and cons are there.


3. Constant, as long as you're dealing with scalars.

Regards
Peter

-- 
hype
WWW: http://plphp.dk / http://plind.dk
LinkedIn: http://www.linkedin.com/in/plind
BeWelcome/Couchsurfing: Fake51
Twitter: http://twitter.com/kafe15
/hype

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] How to store data that doesn't change?

2010-09-15 Thread Ashley Sheridan
On Wed, 2010-09-15 at 08:46 -0400, Peter van der Does wrote:

 Hi,
 
 How do you people store data that doesn't change, an example of this
 would be the version number of your software. You might want to use it
 through out your program but how to you store it?
 
 As far as I can see there are several options to use this data.
 1. Global Variable
 2. Store it in a registry class
 3. Store it in a named constant.
 4. Use a function that will return the data (kind of like a regsitry
 class but it's not a class)
 
 Personally I don't like option 1 but what about the other options. Is
 any of them faster then the others. What other pros and cons are there.
 
 -- 
 Peter van der Does
 
 GPG key: E77E8E98
 
 IRC: Ganseki on irc.freenode.net
 Twitter: @petervanderdoes
 
 WordPress Plugin Developer
 Blog: http://blog.avirtualhome.com
 Forums: http://forums.avirtualhome.com
 Twitter: @avhsoftware
 


I'd go with a constant, for the simple reason that it means the variable
can't and shouldn't change in the execution of the script. The constant
could be within a class or a global, however you prefer. There will be
slightly more memory used in a class, but it avoids the constant from
conflicting with others in the script possibly.

Creating a whole function or class for this does seem a little overkill
probably, so a simple global constant should do the job really.

Thanks,
Ash
http://www.ashleysheridan.co.uk