On 10/16/07, Ala'a Ibrahim <[EMAIL PROTECTED]> wrote: > > about DB abstraction layer (I guess you mean something like DB Engine > Common interface, a DB abstraction layer is highly recommended, but not a > common interface), well depends on what are you doing, a specialized system > or an off-the-shelf application, small or big ..., but in the end if you > are, or not using a DB Common Interface, stick to a DB layer, where you > throw all the sqls there. > about Templating systems, well you should look for what they offers, the > problem is that people use a templating engine without using any of it's > features, just an extra burden on your application. for example, smarty have > a very useful caching features. Unless you are using them, then stick with > php templating syntax. > > about speed, well com'on, these things are not going to cost much, also a > lot of opcode caching engines are available, which would fix the extra > burden of an organized code, if you want to come to it, adding comments to > your code would add a little time for php parser, but that is not an excuse > for not writing comments,
Actually, this is not true, even if you don't use an opcode cacher. The reason is that the parse tree needs to be built anyway. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Jordan PHP Users Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/JoPHP http://Jolug.org/ -~----------~----~----~----~------~----~------~--~---
