CS 5314: Concepts of Programming Languages
Spring 2016

Programming Projects

• Regular Expressions in Python
• Calculating Sports Team/Player Stats Using Higher Order Scheme Functions

  Updated TestData-Team_scoring_list.rkt file (9:07pm April 3); This file replaces the file listed below as test data for Team_scoring_list.rkt.
  TestData-Team_scoring_listRev.rkt

  Below find 2 files to use to test your Scheme project. They each contain several test cases that correspond to one of the input lists in the project, and to the corresponding functions. This is the complete set of test data EXCEPT test case #7, which we will have answers for ASAP.

  A few Scheme project clarifications:

  • Since we are dealing with floating point numbers and some might be repeating decimals, we are adding the requirement that all floating point values be rounded to TWO decimal points. Note that using a helper function with the built-in round function can be used to accomplish this easily as you compute these values.
  • You can assume that all players on a team in any of our input lists will have different names. DO NOT CHECK for this.
  • For final submission and ease of grading, please put all your function definitions with their corresponding function applications to each of the provided test data cases in the order they were specified, all in one file to submit. The test data files have been formatted to help you do this.
  
  
  Test Data for Scheme project:
  TestData-Team_Record_list.rkt last revised 04/06/2016 3:04pm
  TestData-Team_scoring_list.rkt TestData-Team_scoring_list.rkt last revised at 9:03pm 04/03/2016.

  Note: There was a question about test2 in the Team_Record_list test data, that referred to the order of the elements in a list. We agree that the first posted data had the elements in an unexpected order -- and we changed this in the new posted test data. HOWEVER, for the non-top-three functions these lists are really acting as sets, so that having the correct elements in each list matters, but their order is not really an issue for correctness.

  
  Scheme grading rubric
• Prolog type checker
  
  

  February 22, 2016 The current Prolog assignment is flawed by the problems we have had with the input tokenizing Prolog routines; these routines have not provided the tokens in the manner expected, especially the problems with the string tokens. Some of this is due to change between 2 different Prologs, but not all the problems stem from that. Frankly, the I/O in this assignment was not intended to be so challenging. From the messages on Piazza.com students have been struggling with these issues too much, rather than with programming Prolog.

  Therefore I am changing the specifics of the assignment:
  1. Part 1 of the Prolog programming assignment that is scalar variables without the string datatype is due Friday Feb 26th. I am hoping we will get the tokenizer working with string data in time to include strings in the final turn-in of the assignment on March 2nd.
  2. Part 2 of the Prolog programming assignment -- adding structs containing only scalar variables — will be due (together with a working part 1) on March 2nd
  3. Part 3 of the Prolog programming assignment is hereby ELIMINATED. If anyone wants to solve part 3 they can present it for grading as EXTRA CREDIT in the course.
  

last changed at 10:04pm on April 16, 2016 by BGR