Comments on: Why should we use PHP constants inside classes http://thedeployer.com/2009-04-why-should-we-use-php-constants-inside-classes Technology and Development Today Sat, 03 Apr 2010 08:03:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: anonymous http://thedeployer.com/2009-04-why-should-we-use-php-constants-inside-classes/comment-page-1#comment-60 anonymous Sat, 20 Jun 2009 12:55:31 +0000 http://thedeployer.com/?p=237#comment-60 "dezactivate", yeah right ;)) “dezactivate”, yeah right ;) )

]]> By: Lucian Daniliuc http://thedeployer.com/2009-04-why-should-we-use-php-constants-inside-classes/comment-page-1#comment-28 Lucian Daniliuc Thu, 16 Apr 2009 06:31:40 +0000 http://thedeployer.com/?p=237#comment-28 Well, I have to disagree. I use subversion for all my projects and my config file IS a class. There's no need to add code in the configuration class. And regarding versioning config files, I keep in the repository files like config-dist.php, and after deployment I rename them to config.php. Well, I have to disagree. I use subversion for all my projects and my config file IS a class. There’s no need to add code in the configuration class.

And regarding versioning config files, I keep in the repository files like config-dist.php, and after deployment I rename them to config.php.

]]> By: ZacharyDanger http://thedeployer.com/2009-04-why-should-we-use-php-constants-inside-classes/comment-page-1#comment-27 ZacharyDanger Wed, 15 Apr 2009 20:32:39 +0000 http://thedeployer.com/?p=237#comment-27 Storing database configuration (any configuration, really) information inside a class is bad form. If you're using any sort of version control system, you now have to template your AppSettings class. Storing database configuration (any configuration, really) information inside a class is bad form. If you’re using any sort of version control system, you now have to template your AppSettings class.

]]>