On 19 July 2007, Erick Tryzelaar wrote: > On 7/17/07, skaller <[EMAIL PROTECTED]> wrote: >> The problem is .. Emacs and Gvim can already do this.. >> so why do all that work and have a substandard >> text editor? > > I've used python's all the time, I find it super useful to test out > small things. I've always wanted one for felix, but I'm not sure how > we can pull it off since we need to go through a c++ compiler, which > can take a lot of time.
I like the Emacs method but it is really the same thing as invoking the shell from Emacs and it needs a makefile unless you are using ellcc; gdb from Emacs is better (you can test different expressions and values and continue the program from there). Nothing matches Python's editor, even on Windows and OCaml's is wretched (it really needs something like readline). There might be a way to do interpreted code with a hook through CINT <http://root.cern.ch/root/ Cint.html>. So that could handle code generation and execution; for parsing the command line it would take a lot of work, even sponging off of readline and the current parser, because each statement would have to be wrapped with the current environment. The only alternative would be a bytecode interpreter and that involves a whole separate VM--even Neko would require significant translation from felix output. Cheers, Pete ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
