Stephen R. van den Berg wrote:
Martin Nilsson (Coppermist) @ Pike (-) developers forum wrote:
Right now I would prefer to not compile and put that code in the global name space every time Pike is started. Perhaps put it in Val for now.
Another option would be to make two (or more) versions of these types: - One very basic version without operators in a easily accessible global spot. That should be very small codewise (the objects themselves only store one to max three integers) and even more lightweight to compile. - Another more advanced version of these types can inherit the basic version and then add operators.
For the SQL subsystem, the basic versions would be fine, we merely need a way to store and retrieve the values. Not even _encode/_decode is needed. Having a cast-to-string that is SQL parseable is a plus, but even that could be stripped and moved into an SQL private inherit of these types.