Scribd Logo
Upload

Welcome to Scribd!

  • Lecture Slides Section2 21 Records

    Uploaded by

    orchid21
    18 views4 pages
    This document provides an overview of records in programming languages. It states that records have fields that hold values and record types have fields that hold types. The order of fields in a record value or type does not matter. Records are built by specifying fields and values, and individual fields can be accessed by name. The document gives an example record and discusses that records are more readable than tuples when there are many fields. It notes that some languages allow referring to arguments or fields by position or name.

    Original Description:

    sml

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document provides an overview of records in programming languages. It states that records have fields that hold values and record types have fields that hold types. The order of fields in a record value or type does not matter. Records are built by specifying fields and values, and individual fields can be accessed by name. The document gives an example record and discusses that records are more readable than tuples when there are many fields. It notes that some languages allow referring to arguments or fields by position or name.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    18 views4 pages

    Lecture Slides Section2 21 Records

    Uploaded by

    orchid21
    This document provides an overview of records in programming languages. It states that records have fields that hold values and record types have fields that hold types. The order of fields in a record value or type does not matter. Records are built by specifying fields and values, and individual fields can be accessed by name. The document gives an example record and discusses that records are more readable than tuples when there are many fields. It notes that some languages allow referring to arguments or fields by position or name.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 4

    Programming Languages Dan Grossman 2013

    Records

    Records
    Record values have fields (any name) holding values {f1 = v1, , fn = vn} Record types have fields (and name) holding types {f1 : t1, , fn : tn} The order of fields in a record value or type never matters REPL alphabetizes fields just for consistency Building records: Accessing pieces: #myfieldname e (Evaluation rules and type-checking as expected)
    Jan-Mar 2013 Dan Grossman, Programming 2

    {f1 = e1, , fn = en}

    Example
    {name = Amelia, id = 41123 - 12} Evaluates to {id = 41111, name = Amelia} And has type {id : int, name : string} If some expression such as a variable x has this type, then get fields with: #id x #name x Note we did not have to declare any record types The same program could also make a {id=true,ego=false} of type {id:bool,ego:bool}
    Jan-Mar 2013 Dan Grossman, Programming 3

    By name vs. by position

    Little difference between (4,7,9) and {f=4,g=7,h=9} Tuples a little shorter Records a little easier to remember what is where Generally a matter of taste, but for many (6? 8? 12?) fields, a record is usually a better choice A common decision for a constructs syntax is whether to refer to things by position (as in tuples) or by some (field) name (as with records) A common hybrid is like with Java method arguments (and ML functions as used so far): Caller uses position Callee uses variables Could do it differently; some languages have
    Dan Grossman, Programming 4

    Jan-Mar 2013

    You might also like