Displaying 4 results from an estimated 4 matches for "bicapitalizedidentifiernames".
2009 Apr 12
9
[LLVMdev] Porting LLVM backend is no fun yet
.... When I better get the hang of all of this, I
expect to have some ideas on how to improve TableGen. Is there a
development plan or wishlist for TableGen? I see nothing on the wiki yet.
I must also say that the LLVM code is considerably "denser" because of
the unfortunate choice of BiCapitalizedIdentifierNames. Underscores
lend some horizontal whitespace to names and make their subtokens
visually distict. BiCapped code is kinda like German with its
cumbersome compound nouns.
Enough complaining for now--back to banging skull on stone! 8^)
G
-------------- next part --------------
An HTML attachme...
2009 Apr 13
0
[LLVMdev] Porting LLVM backend is no fun yet
...ng of all of this, I expect to
> have some ideas on how to improve TableGen. Is there a development
> plan or wishlist for TableGen? I see nothing on the wiki yet.
>
> I must also say that the LLVM code is considerably "denser" because
> of the unfortunate choice of BiCapitalizedIdentifierNames.
> Underscores lend some horizontal whitespace to names and make their
> subtokens visually distict. BiCapped code is kinda like German with
> its cumbersome compound nouns.
>
> Enough complaining for now--back to banging skull on stone! 8^)
-------------- next part -------...
2009 Apr 13
0
[LLVMdev] Porting LLVM backend is no fun yet
...;s true it could be harder to port LLVM to certain
architectures. But it's probably not the case for every target. Can
you do a good port of x86 using CGEN? :-)
Evan
>
> I must also say that the LLVM code is considerably "denser" because
> of the unfortunate choice of BiCapitalizedIdentifierNames.
> Underscores lend some horizontal whitespace to names and make their
> subtokens visually distict. BiCapped code is kinda like German with
> its cumbersome compound nouns.
>
> Enough complaining for now--back to banging skull on stone! 8^)
>
> G
>
> ___________...
2009 Apr 13
0
[LLVMdev] Porting LLVM backend is no fun yet
...of the TargetInstrInfo
hooks automatically. There's no plan for things like this at the
moment though; they will get done only when someone steps up
and implements them.
>
> I must also say that the LLVM code is considerably "denser" because
> of the unfortunate choice of BiCapitalizedIdentifierNames.
> Underscores lend some horizontal whitespace to names and make their
> subtokens visually distict. BiCapped code is kinda like German with
> its cumbersome compound nouns.
I guess this is just a matter of familiarity, and perhaps of choosing
an advantageous font.
Dan