Shlomi Fish
Tue, 09 Apr 2002 12:32:16 -0700
On Tue, 9 Apr 2002, guy keren wrote:
>
> On Tue, 9 Apr 2002, Shlomi Fish wrote:
>
> > I believe switching to Lex and Yacc will allow adding new features much
> > more easily. So it may be a good idea to invest a lot of time now, only so
> > one can later make sure that easy changes easy. It's like trying to
> > portably build a DLL without using GNU libtool. Doable, but much easier
> > with the latter.
>
> ok. so where is the code?? if you just want to have a meeting in order to
> convince us to write it - spare the time for something else. if you so
> want to see it done - you'll have to do it. now, lets break this loop - i
> don't see a point in such a meeting - convincing the convinced is
> pointless.
>
Fine, let's just have a meeting. We'll discuss lex, yacc, syscalltrack in
general, the SSSCA (Orr, do you intend to update your U.S. Laws lecture),
Life, the Universe and Everything. Maybe I can take a look at the code and
actually hack something in Perl/Lex/Yacc that will compile the
configuration file into a C code that loads it, compiles it with gcc and
run the compiled file. That's my plan for the initial release, as I'd
rather not create bindings for everything that sct_ gives me.
My demo was just a suggestion. It may actually attract more people (like
Orna) who wish to see how those two tools work.
> i do see a point to a lecture for the _club_ about lex and yacc - but you
> already stated you won't give one. i might think of giving one myself,
> then - though i'll have to re-learn the subject... and it'll have to wait
> until sometime after the multi-threading session.
>
Agreed. I can help you with that. My constructive suggestion is for you to
use Perl because writing a compiler or interpreter in Perl is so much
straightforward than in C. (that's one of the things I don't like about
the Dragon Book, which I read at present) And Perl supports Lex and Yacc.
You can later demonstrate a small project in C, just to show how to use it
there, but demonstrating everything in C would be insanity. Don't take it
wrong, but I think it made your Gtk+ lecture, much less effective.
I hate giving C code as an example. That's what Perl or Python or Lisp (or
Haskell? Sorry could not resist) and other fast protoyping languages are
for. To demonstrate things. Maybe writing vertical applications is better
in C in the long run. But not demonstrating stuff.[1]
Regards,
Shlomi Fish
[1] - It reminds me of someone. He studies in an English university with
Java, so he wrote a funny pseudocode in it. I corrected his code and
generally told him that it was a bad idea to do it with Java. Java may be
a good language to teach programming courses in, but again, any language
where you have to type System.out.println to print a string to the screen
is not a fast prototyping language.
> --
> guy
>
> "For world domination - press 1,
> or dial 0, and please hold, for the creator." -- nob o. dy
>
--
----------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/
Home E-mail: [EMAIL PROTECTED]
He who re-invents the wheel, understands much better how a wheel works.
--------------------------------------------------------------------------
Haifa Linux Club Mailing List (http://linuxclub.il.eu.org)
To unsub send an empty message to [EMAIL PROTECTED]