Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

MAY LISP HELPS

Name: Anonymous 2010-09-17 17:31





                 ∧_∧    / ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄
              ( ´∀`) < Nyan nyan nyan nyan ni hao nyan
            /    |    \________
           /       .|     
           / "⌒ヽ |.イ |
       __ |   .ノ | || |__
      .    ノく__つ∪∪   \
       _((_________\
        ̄ ̄ヽつ ̄ ̄ ̄ ̄ ̄ ̄ | | ̄
       ___________| |
        ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| |
        ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| |
       ___________| |
        ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| |

Name: >>2 2010-09-18 10:37

>>8
Yes, my (>>2) parser is only about 40 lines.
Also, if one were to introduce a struct-like data type, how would you do it? For a struct foo { int bar; }, I've thought about:
(foo bar) - Feels Sepplesy, what with 'calling' a struct like it's a function (i.e. overloading)
(foo.bar) - Adds more grammar
(get-member-of foo 'bar) or similar - could have to involve some hash function or other (slow), unless it's done at compile-time

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List