On Thursday 26 August 2010, Bill Hoffman wrote: > > I colleague hit this today (i.e. the code was accepted), and was > > surprised that cmake did not report an error on this. > > > > Instead of a warning and continuing I'd prefer a policy actually. I'd say > > it's a bug that it doesn't fail. > > It will break too much code. If we give a warning and continue that > should be fine. > This has been allowed for 10 years so I am guessing there are lots of > instances of this floating around.
So, no policy ? With a policy it would warn and continue, except when the policy is set to NEW, then it would fail. Alex _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
