Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - camperman

#1
Anything else we might add? /
September 15, 2007, 05:13:09 AM
No problem! Work and personal stuff have got in the way of my newlisp learning curve for a year or so now (as you can probably tell from the timestamp in the mixer project sources) but I'm getting back into it as of this week :)



I still really want to do a small game - perhaps a platform type - with newLisp and SDL so I'm watching oofoe's work with great interest.





/cm
#2
Anything else we might add? /
September 14, 2007, 03:48:38 PM
Quote
If you do a search for SDL on this message board, there's a reference to someone's project using the SDL_mixer, including a music file player. Unfortunately, the site seems to be down, but you might be able to find it in the Google or Wayback Machine cache.


That would be mine - it's up again at http://www.77000rpm.com/newlisp/">http://www.77000rpm.com/newlisp/
#3
Anything else we might add? /
June 27, 2006, 04:18:24 PM
newLISP doesn't mind if you use other languages - it will talk to you anyway



newLISP: the structure and interpretation of real world applications



newLISP: small is beautiful (when it works)



newLISP: because context is everything in interpretation <- I'm very proud of this one :]



newLISP: because there's nothing wrong with your C code



newLISP: write once, run everywhere (this might have been taken I think...)
#4
newLISP and the O.S. /
June 22, 2006, 06:16:23 AM
Duh - I forgot about the n. Thanks Lutz - all works fine now.
#5
Hi all,



I'm trying to duplicate Larry Clapp's rather nice little hack which allows vim to communicate with CL via a pipe - except using newLISP (of course) and a socket connection. Ultimately I want to write a vim plugin that lets you send sexps and buffers to a running newLISP process.



So I start up newLISP like so:



newlisp -d 1234



and then I test from python:



ipython:



import socket

host = "localhost"

port = "1234"

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)

s.connect((host, port))

s.send("(+ 10 10)")

>> 8                       # no of bytes sent

s.recv(1024)

>> 'newLISP v.8.8.0 on linux.nn> '



And now I'm stuck. I can't see how to either a) get the newLISP process to echo results back to me or b) to actually see what it's doing. Should I do this in a handler?



TIA...
#6
Anything else we might add? /
June 17, 2006, 05:18:15 PM
an uncommon kind of LISP :)
#7
newLISP newS / SDL mixer for newLISP
June 17, 2006, 05:12:13 PM
Grab it here:



http://www.77000rpm.com/newlisp/">http://www.77000rpm.com/newlisp/



There's also a simple example player which will play your MODs/ITs/XMs/WAVs/MP3s/OGGs and whatever other format your copy of SDL_mixer was compiled with :)



The player worked first time which was kind of disturbing - that's only ever happened to me with Python...
#8
newLISP newS /
June 12, 2006, 09:35:28 AM
QuoteI saw the same exchange by following a link there from reddit titled:


Quote from: "foobarbaz, on reddit"Why is Lisp unpopular? Maybe it's a

"community" like this. (Read first 10 posts to see what's happening.)




Good grief. Newbie asks beginner question and gets trojan in response! Mind you, that just about sums up c.l.l for me. I won't miss it.


Quote
Group (b)

   Smalltalk

   BASIC

   Ruby

   Scheme

   Lua

   newLISP

   

You can add Python to Group (b) - laid-back, friendly and helpful community.
#9
newLISP newS /
June 12, 2006, 03:47:24 AM
Quote from: "pjot"Howdy camperman!



Welcome to newLISP, the best programming language on earth. :-)



Indeed a (load "GL.lsp") is all. Please let me know if you run into trouble, I am happy to help out.


Thanks Peter. No problems so far running the demos on your page.


QuoteThe GLU context could be rewritten in newLISP completely, by the way. I already rewrote the GluLookat function, but the whole GLU API should be translated. In this way, newLISP will only depend on 1 shared object/DLL. Also some float/double mixups can be avoided. So if you have some sparetime, and need some exercise... ;-)


I'll be happy to help once I know enough - I'm not there yet though. Still trying to get newlisp.vim to look pretty...
#10
newLISP newS /
June 11, 2006, 12:43:28 PM
Thank you Lutz - and thanks very much for the links. I'm a bit confused though. Apparently all I have to do is:



(load "GL.lsp")



and then call the function like:



(GL:glBegin ...)



Is that all? No fighting with ASDF? No random segfaults? No different behaviour between Linux and Win32? No compile errors? No insults from #lisp?



newLISP certainly has a long way to go before it matches the CL experience - hehehe. </sarcasm>
#11
newLISP newS /
June 11, 2006, 07:35:19 AM
Thanks! I have a couple of cross-platform game projects in the pipeline: one needs to be scripted in Lisp and the other will probably (now) be written in newLISP calling the SDL and OpenGL shared libraries.



I just googled for "lisp small linux win32 macosx scripting" and the newLISP home page came up first. Bingo. I don't know why I didn't notice it before - I've been looking around for about six months for something suitable.
#12
Hi all,



I've been getting thoroughly depressed since discovering Lisp through Paul Graham's essays two years ago and then bumping my head against every single issue that Steve Yegge mentions in his essay here  http://tinyurl.com/g95n9">//http://tinyurl.com/g95n9. It has been mortifying to read through say, Norvig and see the sheer power of CL in action and then waste hours and hours getting simple libraries to work with any of the implementations I tried.



newLISP Just Worked. Out of the box. First time. Linux, Windows, MacOS, it's embeddable, it's clean.  It's Lisp for the real world in 2006 and I just wanted to say thanks for er, putting the fun back into Lisp. You guys should make that your motto - oh wait, you already have :)