You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Computation Club mailing list
Hi all,
Before we forget: we agreed to hold the next meeting in TWO WEEKS, July 21st, because Leo will not be around on the following Tuesday. (Note that the 21st is the day after Brighton Ruby, which several of us are attending.)
Would anyone be willing to summarise/propose what we’re planning to do next time?
Cheers,
-Tom
Murray Steele
unread,
Jul 12, 2015, 6:00:36 PM7/12/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Computation Club mailing list
On 8 July 2015 at 20:29, Tom Stuart <t...@codon.com> wrote:
Would anyone be willing to summarise/propose what we’re planning to do next time?
We decided that this next meeting will be about Chapter 12 even though we didn’t manage to finish practical for Chapter 11 in our last meeting[1]. The feeling from the group was that we didn’t really feel up to another session shouting at the vim-operator-du-jour because we’re all confused about when we had to call tokenizer.advance.
We decided that finishing the jack-compiler[2] was an exercise best left up to the reader. There was some discussion that the approach suggested by the book might’ve made our current compiler hard to evolve a reasonable solution out of and at least one person said they might take a few steps backwards and re-implement the compiler from an earlier point.
Even if no-one completes a compiler and we need one for the Ch12 practicals we can always use the one provided by the authors of the book[3].
Aside: I’m not entirely sure I’ll be able to make the Ch12 meeting, so as atonement I’ve spent some time being confused about tokenizer.advance all on my own and pushing our existing compiler towards completion[4]. Feel free to have a look and leave any comments; although do note that I’m aiming for it to be functionally complete, not well designed ;).