| // The MIT License | |
| // Copyright (c) 2019 Sanghyeon Jeon | |
| // Permission is hereby granted, free of charge, to any person obtaining a copy | |
| // of this software and associated documentation files (the "Software"), to deal | |
| // in the Software without restriction, including without limitation the rights | |
| // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| // copies of the Software, and to permit persons to whom the Software is | |
| // furnished to do so, subject to the following conditions: |
| /** | |
| * !!!! This code doesn't work anymore !!!! | |
| * | |
| * - You can check working code on comments. I won't update this code anymore. | |
| * | |
| * Also, I just decided to remove this code. You can check revisions for old code. | |
| * Since this code was made for discord client that almost 5 years ago, It seems like doesn't work anymore. | |
| * I don't want people keep arguing in the comments, i decided to remove this code. | |
| * | |
| * Note: This code is now fulfilled with Javascript comments. This code won't work even if you pasted to console. doesn't do anything. |
| Lisp interpreter in 90 lines of C++ | |
| I've enjoyed reading Peter Norvig's recent articles on Lisp. He implements a Scheme interpreter in 90 lines of Python in the first, and develops it further in the second. | |
| Just for fun I wondered if I could write one in C++. My goals would be | |
| 1. A Lisp interpreter that would complete Peter's Lis.py test cases correctly... | |
| 2. ...in no more than 90 lines of C++. | |
| Although I've been thinking about this for a few weeks, as I write this I have not written a line of the code. I'm pretty sure I will achieve 1, and 2 will be... a piece of cake! |
