Changes between Version 62 and Version 63 of Records


Ignore:
Timestamp:
Feb 27, 2012 9:23:26 AM (2 years ago)
Author:
AntC
Comment:

Correct an incorrect claim about DORF

Legend:

Unmodified
Added
Removed
Modified
  • Records

    v62 v63  
    6868 
    6969 
    70 The DORF proposal is a variant of SORF with similar goals. However, it only solves the narrow name-spacing issue within a module. If a record is imported into another module, it will still clash. 
     70The DORF proposal is a variant of SORF with similar goals. ~~~However, it only solves the narrow name-spacing issue within a module. If a record is imported into another module, it will still clash.~~~ It is perfectly possible to import Declared Overloaded Record Fields into other modules, and 'share' them in records declared in the importing module (and use the selector function for both the declared records and records imported). Alternatively, if the names are an 'accidental' clash, use qualified naming. (The type system prevents using the 'wrong' selector for a record type.). This is no worse than existing H98 modules/qualified naming. -- corrected by AntC, author of DORF. 
    7171 
    7272DORF and SORF abstract over fields. The benefit of abstracting over field names is being able to write code that works against any Record with a given field. So I can have a function: