Hi, Bankó Ádám wrote: >> Then make a mix of PHP and C code. C call call PHP userland, so it >> shouldn't be a problem. > > I don't want to write a full ORM, only a common base, that others can > extend .. for example with INI/XML file configuration, schema auto > discovery etc. > >> And as I see it, it is always good to have a reference implementation >> in PHP and port it to C. I think Marcus did it while implementing SPL. > > If I'd be doing it Top-down, that clearly would be a good idea. But I'm > doing it with a iterative, XP like method.
you can do the same with XP too. As in PHP so in C you will have to establish a common ground on which the further development will stand on. Then part by part implement in PHP and port to C. Having tests will help a lot. > First I do simple implementations for parts, and then I extend it to > support more features. For example on the first run, the system was > monolithic, now it has database drivers, database types and high-level > types implemented as sub-modules (mostly as polymorphic classes). > > This is not the most effective approach, but it produces working code > early. > > Adam > > Andrey -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
