boost::optional instead of __isset

have you ever considered such substitution? generated objects would be more natural to use (imho ). drawbacks could probably include performance but that would require some tests.
unfortunately such change would break backward compatibility so it would have to be an option to compiler (if ever considered)