Skip to content

Seperation of concerns #1

@tacticiankerala

Description

@tacticiankerala

I played around with the LISP interpreter and I quite liked it :). Awesome job!

When I went through the code, I felt rather than having all the code in one class seperating the concerns would drastically improve readability and maintainability. For example, we can seperate the following responsibilities,

  1. Reading input from user
  2. Parsing
  3. Evaluating

And, if we keep the environment seperately then adding new functions need not have to touch any other part of the system.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions