I can trully say, that i have learned a lot from this project (i looked over the whole code) and i understood some fundamental things of how things work.
All in all, i have a few suggestions:
1.First of all, make functions have some kind of reference params. (One night i wrote something like it, but i find it highly ineficient because i just coppied back the marked variables, perhaps implementing true reference)
2.Make a wrapper to expand the language, adding new functions directly into the parser and executer seems ugly :P
I'm intherested to see where will wsbasic go, but i like to think you have achieved at least one of your goals: To make people understand how an interpreter works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1. Yes that's not difficult. I've implemented reference parameters and regular function params in the matlab compiler I'm writing for my PhD. The problem with doing it in wsbasic is that I beleive that beginners (people starting to learn programming) don't really understand what a reference is, let alone a pointer. But sure, we could put it in wsbasic.
2. Yes that's exactly what I've done with the matlab compiler. I have a couple of students making extensions to the compiler by subclassing the parser and executer class. They put their extensions in the derived class. This can also be done with the wsbasic code. Like this:
#ifndef MYPARSER_H
#define MYPARSER_H
#include "parser.h"
class MyParser : public Parser{
public:
MyParser():Parser(){ ... }
...
};
#endif
So where will wsbasic go? Well KTurtle (an educational app of the KDE suite) is derived from wsbasic. Basically it can go anywhere depending on how mutch time I or someone else has. Sorry to say, for me, that's verry little in the upcoming year. I have to finish my PhD, talk at a couple of conferences and publish some papers...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can trully say, that i have learned a lot from this project (i looked over the whole code) and i understood some fundamental things of how things work.
All in all, i have a few suggestions:
1.First of all, make functions have some kind of reference params. (One night i wrote something like it, but i find it highly ineficient because i just coppied back the marked variables, perhaps implementing true reference)
2.Make a wrapper to expand the language, adding new functions directly into the parser and executer seems ugly :P
I'm intherested to see where will wsbasic go, but i like to think you have achieved at least one of your goals: To make people understand how an interpreter works.
1. Yes that's not difficult. I've implemented reference parameters and regular function params in the matlab compiler I'm writing for my PhD. The problem with doing it in wsbasic is that I beleive that beginners (people starting to learn programming) don't really understand what a reference is, let alone a pointer. But sure, we could put it in wsbasic.
2. Yes that's exactly what I've done with the matlab compiler. I have a couple of students making extensions to the compiler by subclassing the parser and executer class. They put their extensions in the derived class. This can also be done with the wsbasic code. Like this:
#ifndef MYPARSER_H
#define MYPARSER_H
#include "parser.h"
class MyParser : public Parser{
public:
MyParser():Parser(){ ... }
...
};
#endif
So where will wsbasic go? Well KTurtle (an educational app of the KDE suite) is derived from wsbasic. Basically it can go anywhere depending on how mutch time I or someone else has. Sorry to say, for me, that's verry little in the upcoming year. I have to finish my PhD, talk at a couple of conferences and publish some papers...
For a moment there i almost forgot why this project existed and that once i was also new to programming ;-)