From: Nala Ginrut <nalaginrut@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] NYACC version 0.79.4 is released
Date: Tue, 30 May 2017 00:14:45 +0800 [thread overview]
Message-ID: <CAPjoZoexB_4WNczeHQJTq3=E7wFgSW6yv9rH0vBwZhUQLXtwyw@mail.gmail.com> (raw)
In-Reply-To: <8DAE5ED0-CF1B-47BB-944A-7295265F17C9@gmail.com>
Maybe not implement it with Guile native string, just take advantage of
bytevector.But there must be an abstract layer.
I will try to implement ES6 when I finish guile-lua-rebirth. I think
guile-es6 could provide another concurrent framework based on delimited
continuations different from call back hell in nodejs.
The es6 spec is here
https://www.ecma-international.org/ecma-262/6.0/
2017年5月30日 上午12:06，"Matt Wette" <matt.wette@gmail.com>写道：
>
> > On May 29, 2017, at 8:54 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:
> >
> > Cool! Is the JS parser strict to ES6?
> >
>
> 3rd edition — 1999.
>
> I don’t have a later spec. Is it avaiable?
>
> Also, IMO Guile can’t fully implement ECMAScript because (1) string code
> points are 16 bit, (2) numbers are embedded in 64 bit IEEE floats.
>
> Matt
>
>
>
next prev parent reply other threads:[~2017-05-29 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 4:23 [ANN] NYACC version 0.79.4 is released Matt Wette
2017-05-29 15:42 ` Matt Wette
2017-05-29 15:54 ` Nala Ginrut
2017-05-29 16:06 ` Matt Wette
2017-05-29 16:08 ` Matt Wette
2017-05-29 16:14 ` Nala Ginrut [this message]
2017-06-03 7:03 ` Nyacc parse error tcc.h: DEF_BWL Jan Nieuwenhuizen
2017-06-03 12:59 ` Matt Wette
2017-06-03 13:03 ` Matt Wette
2017-06-03 19:08 ` Jan Nieuwenhuizen
2017-06-03 7:10 ` Nyacc bad escape sequence compiling tcc.h: is_space Jan Nieuwenhuizen
2017-06-03 7:18 ` Nyacc parse error tcc.h: anonymous union in struct Jan Nieuwenhuizen
2017-06-03 15:19 ` Matt Wette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPjoZoexB_4WNczeHQJTq3=E7wFgSW6yv9rH0vBwZhUQLXtwyw@mail.gmail.com' \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).