1. RE: The Source Code
- Posted by kbochert at ix.netcom.com Feb 11, 2002
- 460 views
-------Phoenix-Boundary-07081998- Hi Bernie Ryan, you wrote on 2/11/02 11:47:53 AM: > > >Any idea when the commented source code will be >available ? >I must be pretty stupid because I can't guess how >the the source code fits together yet. >I keep reading how easy it has been for some people >to upgrade the code with all these features and >I'am still trying to figure out the structure of the >interpeter and how everything interacts. I have worked at my modifications for months now, and I am building upon the experience of having written a hand-coded C compiler, and a translator that added classes to Euphoria. To my mind, no one ever knows in detail how an interpreter or compiler interacts with itself. I could never grasp more than a small portion of my own compiler at any one time. >I must confess that when I thought about purchasing >the source that I thought adding something would be >a matter of reading documents and following examples. >Most compilers/interpeters I understand use some form of grammer >with some form of a yacc and a lex; with explaintions of the >emitted byte codes. >I guess I didn't expect a hand coded, hand optimized interpeter. >If everyone thinks that adding featutes is so easy, please >explain to me what I'am missing or not understanding. Its not easy, and you're probably not missing anything. I may call goto easy to implement (3 days), but thats if you don't count the months of learning the source code or the years of learning a debugging style that works in this circumstance. My personal tips: 1) Don't try to understand all the code. Concentrate on the parts that involve your modification. 2) Don't try to understand all the code involved in your modification. Most of it is nit-picking detail. 3) Don't try to understand the code by reading it. Add printf debugging statements and observe what it does when running. 4) Don't try to understand the code right now. Expect to 'add dbg statements-compile-observe results' hundreds of times before enlightenment comes. Karl Bochert -------Phoenix-Boundary-07081998---
2. RE: The Source Code
- Posted by Bernie Ryan <xotron at localnet.com> Feb 11, 2002
- 466 views
kbochert at ix.netcom.com wrote: > > My personal tips: > 1) Don't try to understand all the code. Concentrate on > the parts that involve your modification. > 2) Don't try to understand all the code involved in your > modification. Most of it is nit-picking detail. > 3) Don't try to understand the code by reading it. Add > printf debugging statements and observe what it does > when running. > 4) Don't try to understand the code right now. Expect to > 'add dbg statements-compile-observe results' hundreds > of times before enlightenment comes. Karl: Thanks very much Karl for the tips. Bernie