Re: [fonc] A META-II for C that fits in a half a sheet of paper

[Chris Double]

On Thu, Nov 22, 2012 at 8:54 PM, Long Nguyen  wrote:
> I was very impressed with Val Schorre's META-II paper that Dr. Kay gave me
> to read,

There's a nice META-II walkthrough/tutorial here if people are
interested in trying it online:



Nice job on the C version by the way!

Chris.
-- 
http://www.bluishcoder.co.nz
___
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc

Re: [fonc] Other interesting projects?

[Chris Double]

On 10/05/10 04:59, Alan Kay wrote:

There are already
quite a few Smalltalk elements in Factor (and the postfix language
itself (for most things) could be used as the byte-code engine for a
Smalltalk (looking backwards) and for more adventurous designs (looking
forward)).


Factor already has a Smalltalk implementation (a parser and compiler to 
Factor code) that Slava did a while back as a proof of concept. I'm not 
sure how performant or complete it is however.



Dan Amelang has been moving Nile to a really nice place, and it would be
relatively easy to retarget the OMeta compiler for this (particularly
the JS grounded one) to ground in Factor.


Is there a Nile grammar somewhere? I tried searching for it and didn't 
come up with anything. I see Dan's github repository but it doesn't seem 
to include the Ometa definition.


Chris.
--
http://bluishcoder.co.nz

___
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc

Re: [fonc] git users?

[Chris Double]

On Mon, Jun 16, 2008 at 8:28 PM, Krzysztof Kowalczyk
<[EMAIL PROTECTED]> wrote:
>>
>> The problem that I have is of interleaved changes.  I work for a
>> little on patch A, then patch B, then patch A again, but A and B
>> should be kept separate so that they can be easily reviewed.  A and B
>> may or may have dependencies on one another.
>
> Have a separate branches for A and B? (and then delete them when they
> are merged and no longer necessary).

This is the approach I take for my git repository containing the
import of the Firefox source code. Each patch I work on is in an
individual branch. If patch B depends on A then branch B is based on
branch A and I regularly merge the changes from A to B.

When I need to get the actual patches to send upstream I use 'git diff':

# Patch A
git diff master..A >patcha.txt

# Patch B
git diff A..B >patchb.txt

So the first gets the changes from the original code and the branch A.
The second gets the changes between patch A and patch B.

Chris.
-- 
http://www.bluishcoder.co.nz

___
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc

Re: [fonc] ( picoVerse-:( picoLARC executable code generation ) )

[Chris Double]

On 11/8/07, Kjell Godo <[EMAIL PROTECTED]> wrote:
> I am interested in how executable code is generated in
> general.  Can you point me at any books or info about
> how such things are done?

For a very basic idea of how to do dynamic code generation you might
find my blog post about doing this in Factor a start:



Otherwise any good compiler book should help. Something like Andew
Appels "Modern Compiler Implementation in Java" (he has C and ML
versions too), or Steven Muchnicks "Advanced Compiler Design and
Implementation".

Chris.
-- 
http://www.bluishcoder.co.nz

___
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc