Common acronyms

[Philippe Sigaud]

On Sun, Jan 20, 2013 at 9:23 PM, Nick Sabalausky
<SeeWebsiteToContactMe at semitwist.com> wrote:
> On Sun, 20 Jan 2013 21:09:55 +0100
> "Philippe Sigaud" <philippe.sigaud at gmail.com> wrote:
>
>> Today I saw one thread with DSEL and another with SFINAE.
>> I was wondering, is everyone reading the forums here at ease with
>> the acronyms bandied around?
>>
>> We (I) could create a wiki page to help somewhat, if only to help
>> newcomers not used to the C/C++-specific terms that are commonly
>> used here. Many people here (if not a majority) are also
>> non-native English speakers and I know that *I* had trouble with
>> some words (NIH was new for me). Maybe people can just google it,
>> but it seems friendlier to have a wiki page.
>>
>> Yes? No? Could people here give me some ideas?
>>
>> - RTTI : runtime-time type information
>> (http://en.wikipedia.org/wiki/Run-time_type_information)  <your
>> explanation here>
>>
>> - SFINAE : Substitution Failure is not an Error
>> (http://en.wikipedia.org/wiki/Substitution_failure_is_not_an_error)
>> <your explanation here>
>>
>> - RAII : Resource Acquisition is Initialization <your explanation
>> here>
>>
>> - NIH : Not Invented Here. Also: NIH Syndrome. When a community
>> starts writing its own tools in its own language, (deliberately)
>> ignoring there are more mature tools available elsewhere.
>>
>> - DSL : Domain-Specific Language. A small sub-language dedicated
>> to a particular domain or problem. Examples are regexes, string
>> formatters (%d, %s, ...).
>>
>> - DSEL : Domain-Specific Embedded Language. A DSL used inside a
>> more general programming language. Also known as an internal DSL,
>> as opposed to an external DSL.
>>
>
> CTFE: Compile-Time Function Execution
>
> IFTI: Implicit Function-Template Instantiation
>
> UFCS: Universal Function Call Syntax
>
> AA: Associative Array
>
> ICE: Internal Compiler Error
>

These are good and the first three are very D-centric.

I'd add UDA (User-Defined Attributes)


Do you know where I could put this in the wiki? I suggest in the
Community part, on the right hand side.