Re: [Datadraw-user] BNF in 42

[Questor F. <qu...@fu...>]

I like your ideas and have some comments, but not yet the time to contribute much :(
some thoughts:

1.) if you want to play around with an extensible interpreter have a look at tinypy (http://www.tinypy.org/). it's an interpreter of a subset of python and extensible at runtime...

2.) I vote for tuples to return multiple values (I don't like the c++-way with references/values) because you can quickly see which parameters are put into a function and which parameters are returned

3.) multithreading: the language should support mechanisms to support multiple threads. two paradigms I like: the intel-threading-building-blocks-approach and the csp2-approach. itbb is about work-packages that are handled parallel and csp is about channels and doing the communication via channels between the threads... both are high-level-things and perhaps better in libraries. both paradigmas can be programmed via an event-system.

4.) a good way to debug the user-extensible-modules!!!  but I don't know what "a good way" could be...

happy coding and a happy new year :)
regards
   kai


----- original Nachricht --------

Betreff: Re: [Datadraw-user] BNF in 42
Gesendet: So, 28. Dez 2008
Von: Bill Cox<bi...@bi...>

> On Sun, 2008-12-28 at 11:29 -0500, Richard Prescott wrote:
> > Your are far more experienced then me regarding complex language
> > parsing.  I take your words for granted blindly.
> > 
> > I allow strings in the grammar rules to be lex-style regular
> > expressions.  What do you think?
> > 
> > 
> > That is what I wished.  I was reading about LALR and it seems
> > feasible.
> > 
> > Is your example part of the same syntax of defining relationship and
> > classes or a different syntax on a different file type?
> 
> It's part of the same file.  I may add a "syntax" keyword to introduce
> syntax blocks, but syntax blocks will be part of 42.
> 
> A primary goal of 42 will to be user-extensible.  A 42 interpreter will
> parse the syntax rules, and apply them while reading further code.  It
> remains to be defined, but at certain points in compilation,
> user-defined 42 code can be declared to make modifications to the
> program database.  While the 42 interpreter may have value on it's own,
> the primary output of the 42 translator will be (initially) C source
> code written DatDraw style.  A second output (much harder, but doable),
> will be Verilog output.  DataDraw's use of integer references makes
> hardware compilation of database data structures much more doable.
> 
> > The good point about the previous was cleanness based on
> > indentation...
> > Although, I don't have anything wonderful to propose.
> > 
> > Regards
> > 
> > Richard
> 
> 
> 
> ----------------------------------------------------------------------------
> --
> _______________________________________________
> Datadraw-user mailing list
> Dat...@li...
> https://lists.sourceforge.net/lists/listinfo/datadraw-user
> 

--- original Nachricht Ende ----