I had Win95 running on my 486 dx2 with 4 MB RAM. It worked, but crashed at shutdown. Microsoft said it was the mouse driver or the graphic driver. With 20 MB it didn't crash anymore. Guess Win95 had swapped out code it needed to shutdown, but turned the swap off before finishing the shutdown.
Stop the Blah. If you don't want to answer my posts just don't. Your "an easy XML template engine can only be done with generators" makes you look very stupid. But that's nothing new.
Know it gets funny. You're talking about how stupid I'm about not knowing what I'm talking about, but you can't even type http://php.net/xmlreader and read what it's really about.
BTW, QED: You won't accept any Kid like solution in PHP, because PHP is not Python and it won't be exactly the same. At least I'm sure _you_ couldn't implement it in PHP.
Now if you want me stop criticizing you and the stuff you write you should really learn and understand PHP.
If syntax is not an issue why is perl called a write only language? Both is important. You could use as namespace operator - people should get over it, because it's not the syntax that matters.
You don't understand the difference between someone who writes template and someone who writes code. Only the later needs power. Designers need a little counter or perhaps a modulo for different row colors. View logic isn't really complicated, but it seems like you don't know MVC anyway.
If you want a real pure XML template system it'll always be PITA. Otherwise no one would use XSLT or TAL, because there would be something easier. "Hiding" commands in PIs or cdata is the only way to make it easier.
Why bother implementing an extremely bad languge like Smarty in a very bad language like PHP? Just use the very bad langauge instead: it's faster!
That's what Smarty does. Templates are translated to PHP. Many people made benchmarks and Smarty is nearly as fast as plain unstructured PHP code as template language. That trade-off is because you get an organized view layer. It's the same with every other layer in the classic MVC model.
If you don't like SAX you should take a look at XMLReader. I did take a look at Kid. Something similar should be possible in PHP. Of course it woldn't be exactly the same, because it wouldn't be base on Python, so you'd bash it anyway. One problem I see in Kid is using it for output that's not XML.
I thought of.so when talking about modules. I.e. DSOs in Apache are modules too. Namespaces are on the list of PHP6 IIRC, but I don't know if they've found a symbol for namespaces yet.
ActiveRecord is possible in PHP, just not with the same syntax as in Ruby. You've to create an instance before using it. See CakePHP or Zend Framework for examples.
BTW PHP uses COW. You don't need a reference to an array to avoid copying.
You mean you have only one computer and that's also your server? Otherwise you could use your desktop for development. But if you want to develop on your server you can and may - it's just not something you should do if you're sane. Even if you have to you could change your config - but I've mentioned that in my previous post.
Next point. Static inheritance is not really an OOP thing. There are no school books about how it should exactly work, thus if it's a misunderstanding it means it doesn't work like in language X.
Still - self:: is bound at compile time. That's not an error and will never be. Also not in PHP6. It won't change. PHP6 will add a new keyword static:: that does late binding or at least it's planed. Again: self:: won't change and the way it behaves is not an error.
One thing I also mentioned before - PHP is not Zend's language. Zend is one of the companies working on PHP and providing tools and support for other companies working with PHP. Like Python is not Google's language even if Guido works for them.
BTW I don't believe you've really read the TAL source code. You remember. We're talking about PHP. Plone and Zope have nothing to do with PHP. Kid on the other hand is a much XML as PHP is. You said you hate Smarty because it doesn't work with XML editors. But they won't help you with Kid either, as hiding structure in PIs is not really XML. Maybe you were just looking for a random argument against Smarty.
Oh yeah I read Smarty. It's as complex as such an additional layer needs it to be. Never had a big problem. Never had our designers. Maybe it's because we write PHP code and dummy template and they write HTML dummies and than use our dummy templates to put things together. But I guess working with others is not something someone, who calls everyone an idiot out of the blue or compares him with a random jackass, would think of.
Stop using PHP or get over it. No one really forces you - you could start flipping burgers at McDonalds and never again hear of PHP.
Namespaces are not the same as modules. Modules is just loading a bunch of constructs in the global namespace. You could use PHP with only a minimal set of modules and load what you need at runtime. But that won't work very well in the web enviroment.
BTW how do you know ZActiveRecord was the idea of someone at Zend? There are many people working on the Zend Framework and many of them are not working for Zend.
Last but not least. If you want Python - use Python. It's that simple. PHP will never be Python - why should it?
It seems like you're thinking it needs Zend for any feature in PHP. But PHP is not written by Zend. So it also doesn't matter when and if Zend understands if a feature is needed.
And it is not a bug. At least for self::. There is currently no keyword that can be combined with:: that does not bind at compile time. It would be funny if i.e. parent:: changes just because it's a different instance. Also many languages don't have such a keyword and you have to write the classname explicitly - which also means it won't change. And all of them have ORM libs.
But even in PHP6 it's not a bug that self:: is bound at compile time. What you want is a new keyword that is evaluated at run-time in static context. And that will be static:: IIRC.
I don't know what your problem is with functions with added parameters. That's done in every language and as long as the parameters are optional it's backward compatible. As long as you know under which version your code will run you know which parameters or even function you can use and which you should avoid. Again - like in every other language. If you think feature X of version Y is necessary you'd define that as your minimum version.
The global/single namespace, you seem to have a problem with, is not uncommon in procedural programming languages, which PHP still is. That's why prefixes are used. And you'd prefer the internal functions if performance is an issue.
You should not develop on your live server and try not to debug there either. But even if you need to you could turn display_errors on when you need it - even in a PHP script, because it's PHP_INI_ALL. error_reporting too. Maybe in an auto_prepend_file. RTM.
Now your two posts. T_PAAMAYIM_NEKUDOTAYIM or:: is always using the class it's defined in. Otherwise self:: or parent:: wouldn't work. However it will be fixed in PHP 6. If anyone would have mentioned it when PHP 5 was still in development (before 5.0) the internal structs could have been changed to allow such code. But it took until Ruby on Rails got famous for anyone to need such a feature. Maybe it's because the same thing can be done with an instance - see Zend_Db_Table.
And Smarty. If you want to write your template with XML tools why don't you use TAL? Or output your data in XML and use XSLT to transform it to PHP. If you want to use PHP template engine then just do it! Or you could use Zend_View if you're into libs. But not everyone wants or needs every PHP feature in the view layer and not everyone working with templates should need to learn PHP - or XML and XSLT and XPath and XInclude and... Sometimes you have "designers" write the templates and for them it's easier to learn Smarty.
and ignoring the real solution -- bound parameters -- for years.
That's interesting. I checked the source and oci8.c had ocibindbyname back in 1999. I guess it's similar for other DBs, which had bound parameters years ago. Maybe you should blame mysql - also for the name mysql_real_escape_string().
They also have issues around the monolithic nature of PHP. Oh, you want image processing? Recompile PHP! Oh, you need XML processing? Recompile PHP! There is no isolation whatsoever, everything resides in the same namespace.
It's the same with i.e. Apache - if you don't use shared modules. With php it's cd path/to/extension-source/ phpize configure --enable-your-extension # should be./configure but/. stripped the newline make cp module.so your/lib/path vi path/to/php.ini
And if you weren't an idiot you would come up with real issues instead of replying to everyone who doesn't hate PHP. You see how easy it is to write something like this. I write it and it makes you an idiot - like you made everyone else an idiot. Or maybe you're just wrong and are wasting you're energy for the wrong things.
BTW why are you using Drupal? Any why don't you RTFM or use the recommended php.ini? Notices and display_error should be turned of: "Notice: Trying to get property of non-object in/usr/local/src/drupal-5.0-beta1/includes/session.i nc on line 46" Seems like this makes you an idiot^2.
But... even if it wasn't a user error - how should it be fixed if it can't be reproduced? And if you don't like how the reporter was treated, why did you complain after 5 1/2 years and not in 2001? Also it could be that the new setup replaced a lib of a running webserver and just restarting it is the solution to the problem. That'd mean not restarting it is indeed an user error.
The 12'' Powerbook didn't have a PC card slot and I don't think a 13.3'' MBP would have enough space for one. So if you only want a 13'' MBP you could also live with the MB feature-wise.
A forum thread of Ars Technica recently confirmed that the C2D Macbook will indeed take 3 GB of memory, Apple just doesn't advertise it. Too lazy to search for the link.:)
Maybe because you should have the same RAM size in both slots for the integrated GPU.
Slashdot Mirror
I had Win95 running on my 486 dx2 with 4 MB RAM. It worked, but crashed at shutdown. Microsoft said it was the mouse driver or the graphic driver. With 20 MB it didn't crash anymore. Guess Win95 had swapped out code it needed to shutdown, but turned the swap off before finishing the shutdown.
Stop the Blah. If you don't want to answer my posts just don't. Your "an easy XML template engine can only be done with generators" makes you look very stupid. But that's nothing new.
Know it gets funny. You're talking about how stupid I'm about not knowing what I'm talking about, but you can't even type http://php.net/xmlreader and read what it's really about.
BTW, QED: You won't accept any Kid like solution in PHP, because PHP is not Python and it won't be exactly the same. At least I'm sure _you_ couldn't implement it in PHP.
Now if you want me stop criticizing you and the stuff you write you should really learn and understand PHP.
If syntax is not an issue why is perl called a write only language? Both is important. You could use as namespace operator - people should get over it, because it's not the syntax that matters.
You don't understand the difference between someone who writes template and someone who writes code. Only the later needs power. Designers need a little counter or perhaps a modulo for different row colors. View logic isn't really complicated, but it seems like you don't know MVC anyway.
You're not funny so your karma shouldn't be that bad ;)
If you want a real pure XML template system it'll always be PITA. Otherwise no one would use XSLT or TAL, because there would be something easier. "Hiding" commands in PIs or cdata is the only way to make it easier.
Why bother implementing an extremely bad languge like Smarty in a very bad language like PHP? Just use the very bad langauge instead: it's faster!
That's what Smarty does. Templates are translated to PHP. Many people made benchmarks and Smarty is nearly as fast as plain unstructured PHP code as template language. That trade-off is because you get an organized view layer. It's the same with every other layer in the classic MVC model.
If you don't like SAX you should take a look at XMLReader. I did take a look at Kid. Something similar should be possible in PHP. Of course it woldn't be exactly the same, because it wouldn't be base on Python, so you'd bash it anyway. One problem I see in Kid is using it for output that's not XML.
I thought of .so when talking about modules. I.e. DSOs in Apache are modules too. Namespaces are on the list of PHP6 IIRC, but I don't know if they've found a symbol for namespaces yet.
ActiveRecord is possible in PHP, just not with the same syntax as in Ruby. You've to create an instance before using it. See CakePHP or Zend Framework for examples.
BTW PHP uses COW. You don't need a reference to an array to avoid copying.
Why do you do complex calculations in your view layer? Or are you still using 2.5? Otherwise avoid math.
You mean you have only one computer and that's also your server? Otherwise you could use your desktop for development. But if you want to develop on your server you can and may - it's just not something you should do if you're sane. Even if you have to you could change your config - but I've mentioned that in my previous post.
Next point. Static inheritance is not really an OOP thing. There are no school books about how it should exactly work, thus if it's a misunderstanding it means it doesn't work like in language X.
Still - self:: is bound at compile time. That's not an error and will never be. Also not in PHP6. It won't change. PHP6 will add a new keyword static:: that does late binding or at least it's planed. Again: self:: won't change and the way it behaves is not an error.
One thing I also mentioned before - PHP is not Zend's language. Zend is one of the companies working on PHP and providing tools and support for other companies working with PHP. Like Python is not Google's language even if Guido works for them.
BTW I don't believe you've really read the TAL source code. You remember. We're talking about PHP. Plone and Zope have nothing to do with PHP. Kid on the other hand is a much XML as PHP is. You said you hate Smarty because it doesn't work with XML editors. But they won't help you with Kid either, as hiding structure in PIs is not really XML. Maybe you were just looking for a random argument against Smarty.
Oh yeah I read Smarty. It's as complex as such an additional layer needs it to be. Never had a big problem. Never had our designers. Maybe it's because we write PHP code and dummy template and they write HTML dummies and than use our dummy templates to put things together. But I guess working with others is not something someone, who calls everyone an idiot out of the blue or compares him with a random jackass, would think of.
Stop using PHP or get over it. No one really forces you - you could start flipping burgers at McDonalds and never again hear of PHP.
Namespaces are not the same as modules. Modules is just loading a bunch of constructs in the global namespace. You could use PHP with only a minimal set of modules and load what you need at runtime. But that won't work very well in the web enviroment.
BTW how do you know ZActiveRecord was the idea of someone at Zend? There are many people working on the Zend Framework and many of them are not working for Zend.
Last but not least. If you want Python - use Python. It's that simple. PHP will never be Python - why should it?
It seems like you're thinking it needs Zend for any feature in PHP. But PHP is not written by Zend. So it also doesn't matter when and if Zend understands if a feature is needed.
:: that does not bind at compile time. It would be funny if i.e. parent:: changes just because it's a different instance. Also many languages don't have such a keyword and you have to write the classname explicitly - which also means it won't change. And all of them have ORM libs.
And it is not a bug. At least for self::. There is currently no keyword that can be combined with
But even in PHP6 it's not a bug that self:: is bound at compile time. What you want is a new keyword that is evaluated at run-time in static context. And that will be static:: IIRC.
I don't know what your problem is with functions with added parameters. That's done in every language and as long as the parameters are optional it's backward compatible. As long as you know under which version your code will run you know which parameters or even function you can use and which you should avoid. Again - like in every other language. If you think feature X of version Y is necessary you'd define that as your minimum version.
The global/single namespace, you seem to have a problem with, is not uncommon in procedural programming languages, which PHP still is. That's why prefixes are used. And you'd prefer the internal functions if performance is an issue.
You should not develop on your live server and try not to debug there either. But even if you need to you could turn display_errors on when you need it - even in a PHP script, because it's PHP_INI_ALL. error_reporting too. Maybe in an auto_prepend_file. RTM.
:: is always using the class it's defined in. Otherwise self:: or parent:: wouldn't work. However it will be fixed in PHP 6. If anyone would have mentioned it when PHP 5 was still in development (before 5.0) the internal structs could have been changed to allow such code. But it took until Ruby on Rails got famous for anyone to need such a feature. Maybe it's because the same thing can be done with an instance - see Zend_Db_Table.
... Sometimes you have "designers" write the templates and for them it's easier to learn Smarty.
Now your two posts. T_PAAMAYIM_NEKUDOTAYIM or
And Smarty. If you want to write your template with XML tools why don't you use TAL? Or output your data in XML and use XSLT to transform it to PHP. If you want to use PHP template engine then just do it! Or you could use Zend_View if you're into libs. But not everyone wants or needs every PHP feature in the view layer and not everyone working with templates should need to learn PHP - or XML and XSLT and XPath and XInclude and
Depending on what you're doing the exec functions might be useful. But you should disable dl().
and ignoring the real solution -- bound parameters -- for years.
That's interesting. I checked the source and oci8.c had ocibindbyname back in 1999. I guess it's similar for other DBs, which had bound parameters years ago. Maybe you should blame mysql - also for the name mysql_real_escape_string().
They also have issues around the monolithic nature of PHP. Oh, you want image processing? Recompile PHP! Oh, you need XML processing? Recompile PHP! There is no isolation whatsoever, everything resides in the same namespace.
./configure but /. stripped the newline
It's the same with i.e. Apache - if you don't use shared modules. With php it's
cd path/to/extension-source/
phpize
configure --enable-your-extension # should be
make
cp module.so your/lib/path
vi path/to/php.ini
Where have I recompiled PHP?
And if you weren't an idiot you would come up with real issues instead of replying to everyone who doesn't hate PHP. You see how easy it is to write something like this. I write it and it makes you an idiot - like you made everyone else an idiot. Or maybe you're just wrong and are wasting you're energy for the wrong things.
/usr/local/src/drupal-5.0-beta1/includes/session.i nc on line 46"
BTW why are you using Drupal? Any why don't you RTFM or use the recommended php.ini? Notices and display_error should be turned of:
"Notice: Trying to get property of non-object in
Seems like this makes you an idiot^2.
Why do you have to wait a month? Something with your setup must be wrong if you can't get the recent source from CVS or download the latest snapshot.
So you're one of the sysadmins who don't use the recommended php.ini? It has that name for a reason.
mysql_real_escape_string() calls MySQL's library function mysql_real_escape_string
You can blame mysql. Or just don't use mysql. Or use PDO. And bind parameters instead of a string concat.
sniper is no longer working for PHP.
... even if it wasn't a user error - how should it be fixed if it can't be reproduced? And if you don't like how the reporter was treated, why did you complain after 5 1/2 years and not in 2001? Also it could be that the new setup replaced a lib of a running webserver and just restarting it is the solution to the problem. That'd mean not restarting it is indeed an user error.
But
Only if you're a Lodenfreak. Otherwise it's geladen, du deppata trottl!
The 12'' Powerbook didn't have a PC card slot and I don't think a 13.3'' MBP would have enough space for one. So if you only want a 13'' MBP you could also live with the MB feature-wise.
A forum thread of Ars Technica recently confirmed that the C2D Macbook will indeed take 3 GB of memory, Apple just doesn't advertise it. Too lazy to search for the link. :)
Maybe because you should have the same RAM size in both slots for the integrated GPU.
That wouldn't work for anyone using DomainKeys.