Looks redundant from your description. I can guess at the cause, however. Zend_App actually prepends instead of appending entries to the include_path, so presumably adding the library path in application.ini ensures (depending on order of any other includes) it's at the front of the include_path for performance. Haven't checked so please take that with a a pinch of salt.
In any case, depending on how or where you want the library path, doing from the config file is more flexible. Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Ryan Lange <[email protected]> To: [email protected] Sent: Mon, March 1, 2010 4:07:45 PM Subject: [fw-general] Redundant include paths in Zend_Tool-generated projects? When you create a project with Zend_Tool, it appears to add library/ to the include path twice; once in application/configs/application.ini and again in public/index.php. ========== application/configs/application.ini ========== includePaths[] = APPLICATION_PATH "/../library" ========== public/index.php ========== set_include_path( implode( PATH_SEPARATOR, array( realpath( APPLICATION_PATH . '/../library' ), get_include_path(), ) ) ); Am I correct in assuming that this is simply redundant?
