Yuichi Nishiwaki

@KeenS To cover the all the parts (scheme char) specifies, quite a few static tables with a large number of initial elements (as big as unicode, in short) are necessary....

Great! I can't wait for it :) I love that idea to implement unicode features as an pluggable nitro. Picrin's major policy is to achieve high compatibility with various kinds...

@omasanori I sent you an invitation. Please check it out.

Aw, does that segfault? That should be picrin's fault. I'll check it out.

@kenoss > In Gauche, there is debug print reader macro #?= I definitely agree to this idea. But the literal itself is something we need to discuss further. IMO, `#?`...

@KeenS tree set is enough. and it can be implemented on scheme without c extension 2014-09-26 14:30 GMT+09:00 Sunrim KIM [email protected]: > @wasabiz https://github.com/wasabiz > For set, which type of...

- (picrin base) Most of functions exported from (scheme base) are moved into this library - (picrin list) All functions and macros that manipulates pairs or lists - (picrin vector)...

@stibear Good point!

- (picrin debug) p, pp, macroexpand, ...etc

@KeenS Well, I don't like the idea that changing behavior depending on file extension. If I misunderstand you, that is you are talking about changing extensions of our scheme library...