[Metabang-bind-devel] Re: bind macro

[Gary King]

Yes, I'm doing to warn by default (with a variable to control it and  
choose the behavior for cl:values). That's what has added to the  
complication but it's all a good thing!

On Feb 25, 2008, at 9:32 AM, Attila Lendvai wrote:

>> I've got a lot of projects that use the older syntax, I'm also adding
>> a variable that controls how a binding form like ((values a b) (foo))
>> is interpreted and writing some tests and updating the
>
> Gary, please make an option that if this compatibility variable is
> :warn (or something similar). then a style-warning is issued when bind
> thinks that it's an old VALUES syntax that is going to be interpreted
> as a destructuring-bind. i'd suggest that to be the default value,
> imho that would make the easiest transition for the users.
>
> i remember when :values became mandatory and random spots in our code
> expanded to something unexpected. in fact i sent the patch that
> restored the old behavior after the refactor, but seems like that is
> also biting people, so that's why i think that :warn should make it
> clear what's going on.
>
> -- 
> attila

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM