Changes between Version 15 and Version 16 of Records/DeclaredOverloadedRecordFields/COmpareSORF


Ignore:
Timestamp:
Mar 3, 2012 3:21:06 PM (2 years ago)
Author:
strake888
Comment:

Material wrongly attributed to SPJ deleted

Legend:

Unmodified
Added
Removed
Modified
  • Records/DeclaredOverloadedRecordFields/COmpareSORF

    v15 v16  
    1616The module namespacing in DORF is deliberate, and for exactly the same reason as namespacing in general: a different developer in a different module might 'accidentally' create a clashing name which is unrelated (that is, a name for a field or a record or both). As far as DORF is concerned, these are different names, so need the module name qualification. 
    1717 
    18 In contrast: "The [SORF] proposal ... doesn't allow label names to be scoped: if one module internally uses "field" as a label name then another module can break the abstraction by using the same string "field"." SPJ goes on to discuss a work-round which he sees as "ugly", and concludes "we need scoped instances". DORF does not need any innovations around instances or type inference. 
     18In contrast: "The [SORF] proposal ... doesn't allow label names to be scoped: if one module internally uses "field" as a label name then another module can break the abstraction by using the same string "field".". DORF does not need any innovations around instances or type inference. 
    1919 
    2020'''Wild afterthought:'''