Talk:S-expressions: Difference between revisions
Content added Content deleted
mNo edit summary |
(→Lisp Solutions: If you don't have to build an explicit parser then that should be OK.) |
||
| Line 196: | Line 196: | ||
:Aside from the Python and Ruby implementations, I haven't seen any other languages writing native code back to S-Exps. Perhaps the writer should be spunoff as a separate sub-task? Also, many of the implementations don't show any kind of output. --[[User:Lhignight|Larry Hignight]] 22:28, 22 June 2012 (UTC) |
:Aside from the Python and Ruby implementations, I haven't seen any other languages writing native code back to S-Exps. Perhaps the writer should be spunoff as a separate sub-task? Also, many of the implementations don't show any kind of output. --[[User:Lhignight|Larry Hignight]] 22:28, 22 June 2012 (UTC) |
||
:Unfortunately the task isn't to show a parser but to get the S-expression into an internal form that just happens to be native Lisp. You should show how easy it is to do in Lisp. S-expressions have been used as a data format where much of the processing is done in languages other than Lisp - for example in the Electronics industry. --[[User:Paddy3118|Paddy3118]] 08:51, 23 June 2012 (UTC) |
|||
== TCL native types == |
== TCL native types == |
||