Re: Providing built-in functionality written in PHP (was RE: [PHP-DEV] [VOTE] UUID)

On 06/09/17 13:46, Zeev Suraski wrote: > We’d probably have to be pretty selective in terms of what goes in there – probably just as > selective as we are with the C-based extensions, but I’d imagine that things like ext/exif, UUID, > and perhaps even things like unserialize() could find themselves written in pure PHP using such a > mechanism. My own UUID is a old time UDF add on to the database as the new built in function there does not allow for selection of a Type 1 UUID. UDF is the ideal tool to add functions at the database layer, but it's a pain because it does require C code ... currently. Validation is another area where one often needs to be able to bolt on your own extra functions. Being able to write one's own extensions to things like variable creation or validation is where we are today and writing that functionality optionally in PHP makes sense. The problem is with there being no obvious base to build on. That a variable is often more complex than simply 'int' is a fact, and creating an object for each variable with all of this extra functionality is little different to adding a UUID variable. So a standard method of being allowed to create additional UUID like variables and validate that the supplied data to populate hem is correct. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk