Re: Name for new function

> db_layer? And that would be MySQL specific extension? Doesn't make much > sense to me to introduce extension namespace pollution if it's only for > 1 function that is database specific. I'd actually like to see this as part of Pear. Stig, have we progressed to the point where a Pear module could include a shared extension? Being able to easily move some key functions into a compiled shared extension would be nice. It sort of muddles the division between user-space and language-space though. And this db-layer stuff is definitely something that shouldn't be part of the language itself, but on the other hand I don't want to shut the doors on middle-layer functionality like this either. The issue is where to put it. -Rasmus