Changeset 11247 for lib

Show
Ignore:
Timestamp:
07/06/06 21:39:38 (3 years ago)
Author:
gaal
Message:

* Style.pod - minor tweaks

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • lib/Pugs/Doc/Hack/Style.pod

    r11246 r11247  
    2020  data Val = Int Int | String String | ... 
    2121 
    22 Then readers of code that uses these types may get confused about when 
    23 you are using Val, Int, and String as concrete types and when you are 
    24 constructing a value. 
     22Then readers your code may get confused about when you are using Val, 
     23Int, and String as concrete types and when you are constructing a value. 
    2524 
    2625The following convention is proposed. It can help against this problem, 
     
    5655in constructor and in field names: 
    5756 
     57   -- Aliases always refer to toplevel name, so not "StorageVal" here 
    5858   type EntryStorage = TVar Val 
    5959 
     
    6363      } 
    6464 
    65 Multiple variant records can drop the C<Mk> prefix and start with the 
     65Multiple variant records drop the C<Mk> prefix and start with the 
    6666given name: 
    6767 
    68    type ObjClass   = Class 
    6968   type MutClass   = Class 
     69   type ObjClass   = Class           -- Again, refer to toplevel directly 
     70 
    7071   type ObjId      = Native 
    7172   type ObjSlots   = TVar (Map Ident Val)