Will Kitware consider making CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
default to on starting with 2.6.0 and doing away with this
annoying construct?
Bill is looking into making this implicit. .e.g. if you do not specify the
matching arguments then you are using LOOSE_LOOP_CONSTRUCTS by default. So
On Feb 29, 2008, at 8:00 AM, Sylvain Benner wrote:
Will Kitware consider making CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
default to on starting with 2.6.0 and doing away with this
annoying construct?
I think it would be a cool things to do this.
Soon I will reformat all our scripts to remove
Ken Martin wrote:
Will Kitware consider making CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
default to on starting with 2.6.0 and doing away with this
annoying construct?
Bill is looking into making this implicit. .e.g. if you do not specify the
matching arguments then you are using LOOSE_LOOP_CONSTRUCTS
Bill Hoffman escreveu:
Enjoy!
Wow, that must be a world record... I've mentioned the problem at 10:57
(Brazilian Standard Time), and the solution got committed at 14:18
(BRST). Guinness anyone?? I which my cable TV customer support were that
fast...thanks a lot Bill.
Best Regards,
rod
On Fri, Feb 29, 2008 at 10:40 AM, Ken Martin [EMAIL PROTECTED] wrote:
Will Kitware consider making CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
default to on starting with 2.6.0 and doing away with this
annoying construct?
Bill is looking into making this implicit. .e.g. if you do not specify
On Fri, Feb 29, 2008 at 12:19 PM, Bill Hoffman [EMAIL PROTECTED]
wrote:
Ken Martin wrote:
Will Kitware consider making CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS
default to on starting with 2.6.0 and doing away with this
annoying construct?
Bill is looking into making this implicit. .e.g. if
