Chicken Scheme Websockets(wiki.call-cc.org)
wiki.call-cc.org
Chicken Scheme Websockets
http://wiki.call-cc.org/eggref/4/websockets#quick-start-example
4 comments
Here is an article discussing the utilization of this technique specifically for CHICKEN scheme.
http://www.more-magic.net/posts/internals-gc.html
http://www.more-magic.net/posts/internals-gc.html
This and the paper above were extremely entertaining reads. To the point that I am downloading CHICKEN right now to start exploring. Thank you for those links.
Seconded. That is a great read to help improve your understanding of the C runtime environment (stack frames, longjmp etc).
[deleted]
The example echo server is very elegant.
(with-websocket
(lambda ()
(send-message (string-append "you said: " (receive-message)))))
Thank you. (I'm the author of the library.) It came about after quite a few tries at a good API and with a lot of feedback from other CHICKEN hackers.
It probably isn't very portable right now, unfortunately. It uses a lot of CHICKEN specific things to increase speed and memory efficiency but I'm totally open to making it more portable.
It probably isn't very portable right now, unfortunately. It uses a lot of CHICKEN specific things to increase speed and memory efficiency but I'm totally open to making it more portable.
>It came about after quite a few tries at a good API
I'm very familiar with that cycle. I'm writing a game engine in Guile and I am constantly implementing something, throwing it away, and trying again. Every time you get a bit closer to the API you really want.
>It probably isn't very portable right now, unfortunately.
That's alright. Portable Scheme is cool, but I prefer using what the implementation gives me instead of restricting myself to RnRS. Especially so for something like networking code.
I might never get around to it, but if I find myself wanting to tackle a new project, I'll give porting this a try.
I'm very familiar with that cycle. I'm writing a game engine in Guile and I am constantly implementing something, throwing it away, and trying again. Every time you get a bit closer to the API you really want.
>It probably isn't very portable right now, unfortunately.
That's alright. Portable Scheme is cool, but I prefer using what the implementation gives me instead of restricting myself to RnRS. Especially so for something like networking code.
I might never get around to it, but if I find myself wanting to tackle a new project, I'll give porting this a try.
Makes local and remote io ... quite the same.
[deleted]
Why are people still using languages like scheme? I learned that in university and always hated all those parentheses and thought I would never have to use it again.
> I learned that in university
No you didn't. It is a huge misconception to think that just because you attended lectures, that you learned the material.
It's clear from that comment that you did not learn Scheme.
No you didn't. It is a huge misconception to think that just because you attended lectures, that you learned the material.
It's clear from that comment that you did not learn Scheme.
>thought I would never have to use it again.
See: There is your mistake.
See: There is your mistake.
No, you didn't learn it. Reminds me of this: http://www.psmag.com/navigation/health-and-behavior/confiden...
As for why: because they learned it and are able to recognize problems where using such a language would be beneficial. That's all there is to it, really.
As for why: because they learned it and are able to recognize problems where using such a language would be beneficial. That's all there is to it, really.
To each his own.
Scheme is used a lot in programming language research because it is a very clean and minimal Lisp. It's a great base for experimenting with new language constructs and compilation techniques.
The parentheses is just a thing to get used to, once you have done that you see the structure, not the characters. It 's also a win for research in that no effort need to be wasted on syntax, which usually isn't the object of study anyway.
The parentheses is just a thing to get used to, once you have done that you see the structure, not the characters. It 's also a win for research in that no effort need to be wasted on syntax, which usually isn't the object of study anyway.
Languages like scheme and lisp do not have real syntax, but are more like abstract syntax tree markup languages. That is both the appeal and the dissuasion. Attempts have been made to create syntax for these languages, but it never catches on. https://www.google.com/webhp?#q=alternative+syntax+lisp+%7C+...
I am a fan of Scheme but never got that statement. Why do people say Scheme/Lisp has no syntax? I mean clearly it has a _simple_ syntax, i.e. an expression is either an atom (an identifier, a number, a lambda expression, etc.) or a list of expressions, denoated by "(expr0 expr1 ... exprN). I would say it has a simple, well-thought and powerful syntax.
It has no syntax (of its own) in that it hijacks s-expression syntax instead. When you want to write Lisp code, you actually write some data structures in the s-expression data format, like when writing some data in JSON or XML. Then a Lisp interpreter or compiler uses an s-expression parser to read that data structure into memory, and operates on that.
Then again, not just every Lisp dialect but even pretty much every implementation has its own s-expression parser with its own extensions to s-expression syntax to make it most convenient to write code in, so there's not a very good decoupling after all. :-P Nevertheless it provides some benefits. Like being able to use something like "paredit" to edit code structurally, and making macro systems somewhat simpler (though hygienic macro systems cannot work with pure s-expression data; it must be annotated with lexical context).
You might find it hard to believe but I love Lisp syntax with all of its parentheses, and am explicitly against, for example, Sweet Expressions (SRFI-110). (Though SRFI-105 is fine.)
By the way another meaning of the word "syntax" actually refers to something within the data structures after the actual concrete syntax has been parsed away. For example when you have a list and its first element is the symbol "if", then that list is a usage of the if syntax. This syntax takes three arguments (further elements of the list): a test, consequent, and alternative. So "syntax" is something like a function here, except it operates during compilation and its arguments are unevaluated sub-structures (roughly, code snippets, though the syntax could interpret them however it wants, like for example how the "lambda" syntax's first argument is a parameter list). That's why we can say "in other languages you can only implement new functions; in Lisp you can also implement new syntax." (In the form of macros.)
Then again, not just every Lisp dialect but even pretty much every implementation has its own s-expression parser with its own extensions to s-expression syntax to make it most convenient to write code in, so there's not a very good decoupling after all. :-P Nevertheless it provides some benefits. Like being able to use something like "paredit" to edit code structurally, and making macro systems somewhat simpler (though hygienic macro systems cannot work with pure s-expression data; it must be annotated with lexical context).
You might find it hard to believe but I love Lisp syntax with all of its parentheses, and am explicitly against, for example, Sweet Expressions (SRFI-110). (Though SRFI-105 is fine.)
By the way another meaning of the word "syntax" actually refers to something within the data structures after the actual concrete syntax has been parsed away. For example when you have a list and its first element is the symbol "if", then that list is a usage of the if syntax. This syntax takes three arguments (further elements of the list): a test, consequent, and alternative. So "syntax" is something like a function here, except it operates during compilation and its arguments are unevaluated sub-structures (roughly, code snippets, though the syntax could interpret them however it wants, like for example how the "lambda" syntax's first argument is a parameter list). That's why we can say "in other languages you can only implement new functions; in Lisp you can also implement new syntax." (In the form of macros.)
> It has no syntax (of its own) in that it hijacks s-expression syntax instead. When you want to write Lisp code, you actually write some data structures in the s-expression data format, like when writing some data in JSON or XML. Then a Lisp interpreter or compiler uses an s-expression parser to read that data structure into memory, and operates on that.
My point is that the s-expression format has to be defined (obviously), e.g. you enclose lists in '(' and ')' characters, space symbols separate tokens, etc. In my world these rules are consequences of a defined syntax and saying there is no syntax is just wrong. The reader parses at some point a byte sequence and builds an AST. That Lisp/Scheme has such a simple syntax is a powerful feature of the language but saying it has no syntax just contributes to the belief of misinformed people that Lisp is some kind of strange Voodoo-language which is a bad thing as it is a powerful tool.
My point is that the s-expression format has to be defined (obviously), e.g. you enclose lists in '(' and ')' characters, space symbols separate tokens, etc. In my world these rules are consequences of a defined syntax and saying there is no syntax is just wrong. The reader parses at some point a byte sequence and builds an AST. That Lisp/Scheme has such a simple syntax is a powerful feature of the language but saying it has no syntax just contributes to the belief of misinformed people that Lisp is some kind of strange Voodoo-language which is a bad thing as it is a powerful tool.
It is true that it is a little more nuanced than "has no syntax". The core of the language has very little syntax relative to many of the more popular languages but it still does have some syntax. The confusion also arises because often the syntax it does have looks just the same as function invocation. "or" is syntax whereas "+" is not but they both look the same in invocation. (or fu bar) and (+ 1 2) but "or" is short circuiting and "+" is not. "or" is syntax but it doesn't look like the syntax a lot of people are used to.
In fact, if you use scheme extensively you will probably use more syntax than most languages. Scheme and other lisps are very good at allowing you to create new syntax which is very helpful in creating DSLs which you will run across a lot in scheme libraries and the SRFIs.
In fact, if you use scheme extensively you will probably use more syntax than most languages. Scheme and other lisps are very good at allowing you to create new syntax which is very helpful in creating DSLs which you will run across a lot in scheme libraries and the SRFIs.
This is anecdotal, but I've come to really appreciate the subtle syntax changes that Clojure has adopted. With an editor that provides support for "rainbow" parenthesis I've found Clojure to be the most readable of all the Lisps I've had the pleasure of working with (Guile and Racket among them).
Here's the article: http://home.pipeline.com/~hbaker1/CheneyMTA.html