On Wednesday, February 24, 2016 at 11:49:17 AM UTC+1, Trevor Vaughan wrote:
>
> I'm also a fan of per module which can override a global setting.
>
> If it could be part of the metadata.json, that would be ideal and would
> allow for attestation on the Forge if appropriate.
>
I gave this some thou
On Tuesday, February 23, 2016 at 11:31:18 PM UTC+1, Ben Ford wrote:
>
> Would it be possible in this scheme to mark strict mode per class? I could
> mark my own code as being strict and therefore get compile time failures
> when I make a typo myself, but wouldn't have to enforce that on all third
I'm personally more of a fan of what some programming languages call
interfaces; a sort of contract if you will that a module implements.
So for instance olindata::galera could look for any class that implements
the IMysql interface. That way, I don't really need to worry if the
end-user is us
