search for: unbrac

Displaying 4 results from an estimated 4 matches for "unbrac".

Did you mean: unfrac
2011 Jul 27
0
[LLVMdev] Proposal for better assertions in LLVM
...while allowing the convenient syntax. The voidifier hack is just for types, there are other simple ways to phrase it that boil down to the same construct. You could also implement it in LLVM as: if (!(Ty == STy)) {} else llvm::dbgs() which works as long as its not used as the lone statement in an unbraced else statement. The existing implementations are much more complex in order to support various different constructs. Something like the above would likely serve LLVM's needs. Again, I'm happy to provide a very minimal implementation for consideration if there is interest, I'm just no...
2011 Jul 27
3
[LLVMdev] Proposal for better assertions in LLVM
On Wed, Jul 27, 2011 at 12:51 AM, Chandler Carruth <chandlerc at google.com>wrote: > On Tue, Jul 26, 2011 at 10:41 AM, Talin <viridia at gmail.com> wrote: > >> The assertions in LLVM would be a lot more useful if they could print out >> not only the source code of the expression that failed, but also print the >> values of the various arguments. To that end, I
2006 Apr 04
2
How to apply class from Stylesheet to "link_to" element???
Hi, This is the "img" class for anchor element inside my stylesheet. ===================== A.img:link { color: #ffffff; text-decoration: none; } A.img:visited { color: #ffffff; text-decoration: none; } ====================== I can easily apply this tag inside my html document as follows:- ======= < a href="goodbye.html" class="img"> ======= Now I want to
2011 Aug 09
2
[LLVMdev] Proposal for better assertions in LLVM
...t syntax. The voidifier hack is > just for types, there are other simple ways to phrase it that boil down to > the same construct. You could also implement it in LLVM as: > > if (!(Ty == STy)) {} else llvm::dbgs() > > which works as long as its not used as the lone statement in an unbraced > else statement. > > The existing implementations are much more complex in order to support > various different constructs. Something like the above would likely serve > LLVM's needs. Again, I'm happy to provide a very minimal implementation for > consideration if there...