Displaying 5 results from an estimated 5 matches for "gothcas".
Did you mean:
gotchas
2010 Jul 22
0
[LLVMdev] Casting.h illness
...ast functions).
>
> We generally don't want auto-dereference. There is some special
> magic for unwrapping Uses etc though. Is this what you're in
> contact with Gabor?
>
> -Chris
>
I agree with Chris, that auto-dereferencing is a bad thing (esp.
because of the gothcas I detailed).
I checked in a bunch of fixes to remove auto-dereferencing.
Maybe we should get rid of the type simplifier for (const_)
use_iterator? Sabre what do you think?
There is one thing that is still irritating me:
dyn_cast_or_null and cast_or_null have different interfaces. Should
these...
2010 Jul 22
2
[LLVMdev] Casting.h illness
...gt;>
>> We generally don't want auto-dereference. There is some special magic for unwrapping Uses etc though. Is this what you're in contact with Gabor?
>>
>> -Chris
>>
>
> I agree with Chris, that auto-dereferencing is a bad thing (esp. because of the gothcas I detailed).
> I checked in a bunch of fixes to remove auto-dereferencing.
>
> Maybe we should get rid of the type simplifier for (const_)use_iterator? Sabre what do you think?
Sounds great to me!
> There is one thing that is still irritating me:
> dyn_cast_or_null and cast_or_nu...
2010 Jul 21
2
[LLVMdev] Casting.h illness
On Jul 21, 2010, at 12:49 PM, Eugene Toder wrote:
> Is this a recommended approach/good style/good idea to use
> dyn_cast_or_null<X>(I) instead of dyn_cast_or_null<X>(*I)? (And other
> is and cast functions).
We generally don't want auto-dereference. There is some special magic for unwrapping Uses etc though. Is this what you're in contact with Gabor?
-Chris
>
2010 Jul 22
0
[LLVMdev] Casting.h illness
...ence. There is some special
>>> magic for unwrapping Uses etc though. Is this what you're in
>>> contact with Gabor?
>>>
>>> -Chris
>>>
>>
>> I agree with Chris, that auto-dereferencing is a bad thing (esp.
>> because of the gothcas I detailed).
>> I checked in a bunch of fixes to remove auto-dereferencing.
>>
>> Maybe we should get rid of the type simplifier for (const_)
>> use_iterator? Sabre what do you think?
>
> Sounds great to me!
Okay, soon :-)
>
>
>> There is one thing that...
2006 Apr 10
3
form_remote_tag can only have one submit button?
I setup a form_remote_tag with several submit buttons, all of them share
the same name
( ''do_action'' ) and their values differ.
eg.
button1 named do_action with value ACTION1
button2 named do_action with value ACTION2,
etc
No matter which button I press the value passed is always the one
defined for the first of these buttons ( the correct value associated
with the pressed