Things to look up in the docs

Simen kjaeraas simen.kjaras at gmail.com
Fri Jan 1 06:45:42 PST 2010


On Fri, 01 Jan 2010 11:01:07 +0100, Don <nospam at nospam.com> wrote:

> bearophile wrote:
>> What are the parts of the D1/D2 languages that are both common enough  
>> in programs and not easy to remember, so you need to look them often in  
>> the docs (or in an example list, code snippets list, already written  
>> code, etc)? This list is partially subjective, but probably there are  
>> also some common trends.
>>  For example the syntax of opApply is one of the things I have often to  
>> look up in the docs (while I never need the manual to remember how to  
>> write a generator in Python, that has very similar purposes).
>>  Do you have other parts to add to this list?
>>  Bye,
>> bearophile
>
> is() expressions.

Seconded. Often I end up using is( typeof( { something } ) ) because
it's faster than looking up and understanding how to write the
equivalent isExpression. Yet, I don't have much of an idea of how
to make it better. Is there a DIP for this?

-- 
Simen



More information about the Digitalmars-d mailing list