I am going to download it to play around with the OOP, but I am absolutely shocked that Mysql support is not bundled.
Php 5 Beta 1 Released
I have already informaed PHP support that more than half the PHP programmers wont even TRY PHP 5 beta1 - im not , i found out a few seconds after i downloaded it... i mean, mysql is to me- the most popular database engine used by PHP... and unsupporting it in PHP 5 could of msot likely been the WORST thing they could of done in my opinion - i use mysql on ALL of my scripts, wether its for storing images, or text... i cannot belive it.... id say they r nutz... dont get me wrong... PHP team is the best bunch of people ive heard of yet - creating this free program... but to not support mysql in PHP 5 b1, i think thats just cheeky...
Since when was it not supported???
If you look closer, it's just that the built-in libraries are no longer bundled. Rumour has it, this is due to the difference between the MySQL license and the PHP license. You still should be able to use your own mysql libraries (should be on the system if you've got mysql installed). Do a ./configure --help to figure out how to include them. If you're on Windows, I've got no advice for you. 
well i am on MS Windows... and i meant not bundled... and what license? and does ANY 1 have any idea of putting mysql functions etc into PHP 5 b1 with MS windows XP?
Removed the bundled MySQL client library.
The MySQL client libraries have been GPL'd. That means people that make a living creating PHP/MySQL based solutions that they wish to remain proprietary are forced to buy a license from MySQL to get around the GPL stipulation that there code must be open. This situation may change as there is talk between the PHP dev team and MySQL to work on a solution that may exempt PHP. It's still up in the air, but until a conclusion is reached, MySQL is no longer bundled.
The SQLite extension is now bundled and enabled by default.
SQLite is really not a database, but an SQL interface for a flat file. MySQL is overkill for most sites anyways. It's extremely fast and it can be run anywhere. The host doesn't need a database installed. So for most sites that don't really need all that a RDBMS can offer, or their host isn't capable of providing it, SQLite is really a great alternative. Good for hosts as well.
Originally posted by uniflare
I have already informaed PHP support that more than half the PHP programmers wont even TRY PHP 5 beta1
Well, duh - it's a beta. More than half of all PHP programmers are more interested in just getting their scripts running and wouldn't know a core dump from a stack trace - not the people whom beta releases are intended for.
i don't like OOP...
i am procedural type... so... off after php 5.
4 days later
Came across an interesting essay on the nature of PHP5 and what it means for PHP in general.
Zeev Suraski
...all of the structured code features remain intact. PHP's built-in functions are and will remain procedural.
Did you know that, jimson? (Or learnt anything about the subject since your last post on it)?
then i think i need to reply back to show my respect to weed
Yoda Language starts
basically, i don't like, dislike OOP becoz i cannot agree with the concept of object oriented and the coded resulted from using OOP approach tend to be larger than procedural code where 2 of them actually perform the same function.
one of the logic is, less things(code) easier to manage than large(code) things. this is the main reason why i ditch the oop.
i on with OOP some time ago and the conclusion i got is, OOP will just make the code hard to manage and i am the type that don't want many files appeared to have the app functions or runs.
i view OOP as just a method of grouping variables and functions together inside a class. thats all
they said reusable classes, but u can still reuse your coded procedural functions as u reuse the classes.
from what i experience, OOP just ease your way to obtain and setting variable values. thats all,
with functional procedure, u might need to global and will get mess if u need to global a lot of variables.
so, to show you how much i enjoy the procedural way,
function memory() {
static $data;
switch(func_get_arg(0)) {
case 'a':
$args = func_get_args();
memory_parse($args[1]);
@eval("\$data{$args[1]} = \$args[2];");
break;
case 'g':
$args = func_get_args();
memory_parse($args[1]);
@eval("\$r = \$data$args[1];");
return isset($r) ? $r : false;
break;
case 'dbg':
return $data;
break;
}
}
function a($oMap, $oData) {
return memory('a', $oMap, $oData);
}
function g($oMap) {
return memory('g', $oMap);
}
function memory_parse(&$oMap) {
if(substr_count($oMap, '.') != 0) {
$oMap = explode('.', $oMap);
$oMap = "['".implode("']['", $oMap)."']";
if(substr($oMap, -4) == "['']") {
$oMap = substr($oMap, 0, -4).'[]';
}
} else {
$oMap = "['".$oMap."']";
}
}
i don't think i need to show how to use it, easy to understand code what...
a is for add
g is for get.
might be better if i demo some.
$fruit = array('apple', 'orange', 'banana', 'lemon');
so to add it into the memory, just
a('fruit', $fruit);
if u like, u can
a('country.fruit.', $fruit);
when u g('country.fruit');
u have array like this
$array['country']['fruit'][0] = array(apple, orange .... )
basically, with this function, u can access variable values anywhere in your application, any files as long as the function memory is accessible. this fix the GLOBAL issue.
to debug, just issue
$d = memory('dbg');
print_r($d);
tats all.