Because the installer is the first thing that pops up, I am starting there.
It seems that some very great lengths were taken to obscure the code from the environment. In various places, workarounds were put into place to replace things like register_long_arrays and other assorted things. To what ends must these connections be preserved? The installer appears to function independently from the rest of the project (to an extent). While maintaining the functionality, what liberties can I take with this section of code? Bear in mind my goal is to maintain functionality in a php 4.3+ environment while providing functionality in a php 5 environment. IF we also want forward compatibility with php6 (see bugs.php.net for a list of changes) then the php4.3 compatibility will be in jeopardy (we can cross that river later). So, to summarize, what capabilities MUST the installer retain? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
