Changes between Version 35 and Version 36 of Records/NameSpacing


Ignore:
Timestamp:
Jan 18, 2012 4:09:36 AM (2 years ago)
Author:
GregWeber
Comment:

add Johan's case for name-spacing

Legend:

Unmodified
Added
Removed
Modified
  • Records/NameSpacing

    v35 v36  
    3737 
    3838 
     39== A case for why name-spacing alone is a decent solution == 
     40 
     41 * You can use a type synonym to abbreviate the namespace part (as 
     42shown above.) 
     43 * If there's no ambiguity you don't need to use a namespace (e.g. you 
     44can use 'a' instead of 'Record.a'). 
     45 * The namespace name is predictable (e.g. <Typename>.<fieldname>) 
     46while ad-hoc prefixes tend to use different conventions e.g. the whole 
     47record name (e.g. 'recordA') or some abbreviation thereof (e.g. 
     48'rcrdA'.) 
     49 
     50The main argument for this approach is its simplicity; it's simple to 
     51understand for users and (hopefully) simple to implement. 
    3952 
    4053== Getting rid of the Verbosity with the dot operator ==