Ah Cobol.  I wrote Cobol for years in the sixties.  I used FORTH (a little
bit)  in the seventies but mostly C.  Pascal in the eighties.  Java in the
nineties.  And JS in the 00's.   (And many more not listed).  I'm going to
be pretty busy if I have to do javascript compilers for all those (although
doing so for the javascript language should be pretty easy).

If you are serious about writing a FORTH, let me know.

On Tue, May 28, 2013 at 4:06 AM, Angel Java Lopez <[email protected]>wrote:

> Ah! Very interesting.... Yes, I'm a language geek, I should write a FORTH
> ;*) and use JavaScript for concatenative language.
>
> My first compiler to JavaScript
> https://github.com/ajlopez/CobolScript
> (with ASYNC keyword and a Web site! ;-)
>
> Angel "Java" Lopez
> @ajlopez
>
>
> On Tue, May 28, 2013 at 2:33 AM, Mark Hahn <[email protected]> wrote:
>
>> I have created a new stack language for node and the browser called FJS.
>>  See https://github.com/mark-hahn/fjs.  It is a stack language like
>> FORTH but it uses javascript variables and functions.  It is totally
>> interoperable with Javascript.    It can use any JS module and can create
>> modules to be used by JS.
>>
>>  I'd like to point out one big feature of interest to the Node community.
>> All stack languages easily and naturally support continuations. FJS takes
>> advantage of this to remove the need to code for Javascript callbacks and
>> write code in a pure sync style instead.
>>
>> I just started work on it four days ago but it can already recreate the
>> standard http server node example. See the code for this in the readme
>> file.  It started as a curiosity but it fell together so well it might have
>> a future.  Having a new language start off with the npm library available
>> is awesome.
>>
>> I'm announcing this so early because I am interested in feedback on the
>> concept.  I don't expect it to be used yet.
>>
>> --
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "nodejs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to