Computer Science/164/proj3 - Revision history

Lensovet: Lensovet moved page CS/164/proj3 to Computer Science/164/proj3

2023-02-20T03:51:34Z

Lensovet moved page CS/164/proj3 to Computer Science/164/proj3

Lensovet: /* Milestone 1 */ updates

2009-11-18T22:05:27Z

‎Milestone 1: updates

Lensovet: /* Milestone 1 */ precedence fixed

2009-11-13T03:12:47Z

‎Milestone 1: precedence fixed

Lensovet: /* Milestone 1 */ if/else and args/retvals complete

2009-11-12T06:35:48Z

‎Milestone 1: if/else and args/retvals complete

Lensovet: moved CS/164 to CS/164/proj3

2009-11-12T06:32:02Z

moved CS/164 to CS/164/proj3

Lensovet: tasklist

2009-11-10T07:26:25Z

tasklist

New page

==Milestone 1==
* Fields and methods
*:The starter code supports empty objects and string literals, but it does not support adding fields or methods to objects. You can test your implementation on the provided test-fields.164 file, which also details what fields must support and what syntax you must support. ''This should be done now''.
**basic syntax for put and get
***S -> E[E] = E
***E -> E[E]
**sugar for variable access
***S -> E.E = E → E[E] = E
***E -> E.E → E[E]
**sugar for method calls with self
***S -> def E:id(arglist) { body } → E[id] = lambda('self,'+arglist, body)
***E -> E:Id(arglist) → E[Id](E[Id], arglist)
*If/else and while statements
*:You must add support for if/else and while statements. You can test your implementation on the provided test-ifwhile.164 file.
*Function arguments and return values
*:The starting code supports function calls with no arguments or return values. You must add these features. You can test your implementation on the provided test-functions.164 file.
*Coroutines
*:You must add support for coroutines and the coroutine, yield, and resume expressions. The coroutine expression creates a new coroutine. The resume expression resumes a coroutine from where it last stopped, raising an error if it has already finished. The yield expression yields back to whoever resumed the coroutine. You can test your implementation on the provided test-coroutine.164 file. Unlike functions, you do not have to support a variable number of arguments for resume and yield. Resume takes two arguments, the second of which is passed as an argument to the function (the first time it is resumed) or returned by the corresponding yield (after the first resume). So yield's return value is the argument passed to the corresponding resume.

@@ Line 14: / Line 14: @@
 *:You must add support for if/else and while statements.  You can test your implementation on the provided test-ifwhile.164 file. ''This should be done now''.
 *Function arguments and return values
-*:The starting code supports function calls with no arguments or return values.  You must add these features.  You can test your implementation on the provided test-functions.164 file.  ''This should be done now''. Did some additional testing such as passing a lambda which is then called immediately in the arg list.
+*:The starting code supports function calls with no arguments or return values.  You must add these features.  You can test your implementation on the provided test-functions.164 file.  ''This should be done now''. Did some additional testing such as passing a lambda which is then called immediately in the arg list. ''Now fixed to deal with recursion.''
 *Coroutines
-*:You must add support for coroutines and the coroutine, yield, and resume expressions.  The coroutine expression creates a new coroutine.  The resume expression resumes a coroutine from where it last stopped, raising an error if it has already finished.  The yield expression yields back to whoever resumed the coroutine.  You can test your implementation on the provided test-coroutine.164 file.  Unlike functions, you do not have to support a variable number of arguments for resume and yield.  Resume takes two arguments, the second of which is passed as an argument to the function (the first time it is resumed) or returned by the corresponding yield (after the first resume).  So yield's return value is the argument passed to the corresponding resume.
+*:You must add support for coroutines and the coroutine, yield, and resume expressions.  The coroutine expression creates a new coroutine.  The resume expression resumes a coroutine from where it last stopped, raising an error if it has already finished.  The yield expression yields back to whoever resumed the coroutine.  You can test your implementation on the provided test-coroutine.164 file.  Unlike functions, you do not have to support a variable number of arguments for resume and yield.  Resume takes two arguments, the second of which is passed as an argument to the function (the first time it is resumed) or returned by the corresponding yield (after the first resume).  So yield's return value is the argument passed to the corresponding resume. ''Finally implemented and works regardless of how deeply inside a callstack the yield happens.''

← Older revision	Revision as of 03:51, 20 February 2023
(No difference)

@@ Line 1: / Line 1: @@
 ==Milestone 1==
 * Fields and methods
-*:The starter code supports empty objects and string literals, but it does not support adding fields or methods to objects.  You can test your implementation on the provided test-fields.164 file, which also details what fields must support and what syntax you must support. ''This should be done now. '''However''', the string  x[0]+x[1] gets evaluated as (x[0]+x)[1] instead of (x[0])+(x[1]).''
+*:The starter code supports empty objects and string literals, but it does not support adding fields or methods to objects.  You can test your implementation on the provided test-fields.164 file, which also details what fields must support and what syntax you must support. ''This should be done now. Precedence is now correct as well.''
 **basic syntax for put and get
 ***S -> E[E] = E

← Older revision	Revision as of 06:32, 12 November 2009
(No difference)