On Oct 30, 2015, at 1:56 AM, Eric Botcazou <ebotca...@adacore.com> wrote: >> It won’t. Fixing the language line for the options and a make to ensure it >> still builds for you is enough testing. > > I was talking about the feature itself though, not about the option per se. > The feature is tested for C & C++ but not for ObjC & ObjC++ so there might be > surprises.
We welcome such testing, qualification and bug fixing; not a strict requirement on submissions as far as I know. Some things won’t work well without a concerted effort, and I don’t think it is fair to contributors to require they learn Objective-C/C++ to make such a contribution. All we generally ask for is that what works today, remain working. This usually just means leave the existing hooks in and as code moves around, one has to move the hook around. Whenever a feature conflicts with an Objective feature, I think a nice rule of thumb is that cost is born by the Objective people. We don’t want to make life any more difficult on anyone else. > OK, I can enable the option for ObjC & ObjC++ but this comes with no warranty. Yeah, that’s standard operating procedure.
