- toronto-lisp - mailman3.common-lisp.net

[toronto-lisp] Next meeting Tuesday Mar 2nd
by Abram Hindle 26 Feb '10

26 Feb '10

So we'll meet in March on Tuesday the 2nd. Does anyone want to present anything? * A project you're working on * A problem you have * A solution you've found * A CL feature I can talk briefly about an a tron-ai bot I made for the UW CSC Club competition (it was buggy and I didn't have time to do more about it). abram

2 1

[toronto-lisp] Anyone coming from Waterloo?
by Nikita Sidorov 17 Feb '10

17 Feb '10

Hi, everyone! I enjoyed the meeting in November and would love to join again. But since then I moved to Waterloo and what is more I do not have a car. So, I decided to ask everyone here - is there by any chance anyone coming to meetings from Waterloo and who wouldn't mind company of a lisp admirer? Thanks, Nikita

1 0

[toronto-lisp] AI Tron Competition with support for CLOJURE :D
by Abram Hindle 10 Feb '10

10 Feb '10

http://csclub.uwaterloo.ca/contest/starter_packages.php They provide some support for using Clojure. Basically you program a tron AI. abram

1 0

[toronto-lisp] February Lisp Meet notes
by Abram Hindle 03 Feb '10

03 Feb '10

- Paul brought an old 68000 common lisp print out - Paul talks about lisp works SMP multiprocessing stuff - new threading and sync primitives and interface - parallelism strategies - Hoare Monitors - Dining Philosopher's problem - Exam Dining Philosopher's code - Discuss context switching - doug mentions Lock-free append - spin locks - data type sizes - where 32bit is smaller and faster - where to put - tag in low bits to do math without shift - sbcl & threads - CL def not threadsafe - GCL has plet - Doug says single process-safe is dangerous - CSP http://en.wikipedia.org/wiki/Communicating_sequential_processes - erlang - copy semantics - persistence allowed - stdlib - framework - clojure - - more message passing - socket management - input buffer - output buffer - syscall ammortization - send more messages - pass unix domain sockets - free-lists and warm cache - Djkstra - 1965 dining philosophers problem - JVM - ABCL - CORBA rant -

5 4

[toronto-lisp] Meeting on the 2nd!
by Abram Hindle 01 Feb '10

01 Feb '10

Feb 2nd! LinuxCaffe at 6:00pm. So lets organize and get a few topics on the agenda. abram

2 1

[toronto-lisp] multi-core CL STM
by Paul Tarvydas 22 Jan '10

22 Jan '10

If anyone is not a member of the LispWork lisp-hug mailing list and is interested in multi-core STM, check out Dave McClain's thread entitled "STM": http://www.lispworks.com/support/lisp-hug.html As someone pointed out, the complete multi-core CL implementation of STM fits in one email... pt [may include hoyteisms].

3 3

[toronto-lisp] Toronto Lisp mailing list admin
by Rudolf Olah 20 Jan '10

20 Jan '10

Hey, I'm still the admin for the mailing list, it's weird. So who's taken over the organization of things now? I can log in and change up the admin info and send it over or we can talk to the common-lisp.net mailing list people about how to switch things over. -Rudolf

4 4

Re: [toronto-lisp] toronto-lisp Digest, Vol 25, Issue 5
by Mark Bolusmjak 09 Jan '10

09 Jan '10

I'm using VimClojure (and a few shell scripts) for Clojure and DrScheme for PLT-Scheme. VimClojure seems a little flaky at times. e.g. You start a REPL or evaluate a file and it complains. You try again without doing anything and then it works. The commercial version of IntelliJ Idea has a very solid Clojure plugin (but I don't know if the community version of Idea does/will support it). On Sat, Jan 9, 2010 at 12:00 PM, <toronto-lisp-request(a)common-lisp.net> wrote: > Send toronto-lisp mailing list submissions to > toronto-lisp(a)common-lisp.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://common-lisp.net/cgi-bin/mailman/listinfo/toronto-lisp > or, via email, send a message with subject or body 'help' to > toronto-lisp-request(a)common-lisp.net > > You can reach the person managing the list at > toronto-lisp-owner(a)common-lisp.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of toronto-lisp digest..." > > > Today's Topics: > > 1. development environments (David Penton) > 2. Re: development environments (Vishvajit Singh) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Jan 2010 22:39:36 -0500 > From: David Penton <djp(a)arqux.com> > Subject: [toronto-lisp] development environments > To: toronto lisp <toronto-lisp(a)common-lisp.net> > Message-ID: <8D13BE6F-339E-4294-890E-2402501935D3(a)arqux.com> > Content-Type: text/plain; charset=us-ascii > > I would like to know what development s/w other group members are using for Lisp or Scheme or name-your-poison. > > When I first joined the mailing list Paul Tarvydas and Brian Connoy indicated that they use LW. > > For the moment I am happy with slime+emacs. I use both sbcl and ccl. Anybody else doing slime+emacs? My reason for asking is to pick your brains when I run into trouble ;-) > > Best, > > - Dave - > > > ------------------------------ > > Message: 2 > Date: Sat, 9 Jan 2010 01:16:30 -0500 > From: Vishvajit Singh <vishvajitsingh(a)gmail.com> > Subject: Re: [toronto-lisp] development environments > To: David Penton <djp(a)arqux.com> > Cc: toronto lisp <toronto-lisp(a)common-lisp.net> > Message-ID: > <520868e81001082216w1e7c0c15qaecc644e6721c213(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I'm using SLIME+Emacs, with Clojure as my weapon of choice. > > Funny thing - I'm still running Clojure off of their SVN repository. > Switching over to http://github.com/richhickey/clojure/ is on my todo > list. > > Vish > > On Fri, Jan 8, 2010 at 10:39 PM, David Penton <djp(a)arqux.com> wrote: >> I would like to know what development s/w other group members are using for Lisp or Scheme or name-your-poison. >> >> When I first joined the mailing list Paul Tarvydas and Brian Connoy indicated that they use LW. >> >> For the moment I am happy with slime+emacs. I use both sbcl and ccl. Anybody else doing slime+emacs? My reason for asking is to pick your brains when I run into trouble ;-) >> >> Best, >> >> - Dave - >> _______________________________________________ >> toronto-lisp mailing list >> toronto-lisp(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/toronto-lisp >> > > > > ------------------------------ > > _______________________________________________ > toronto-lisp mailing list > toronto-lisp(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/toronto-lisp > > > End of toronto-lisp Digest, Vol 25, Issue 5 > ******************************************* >

1 0

[toronto-lisp] development environments
by David Penton 09 Jan '10

09 Jan '10

I would like to know what development s/w other group members are using for Lisp or Scheme or name-your-poison. When I first joined the mailing list Paul Tarvydas and Brian Connoy indicated that they use LW. For the moment I am happy with slime+emacs. I use both sbcl and ccl. Anybody else doing slime+emacs? My reason for asking is to pick your brains when I run into trouble ;-) Best, - Dave -

2 1

[toronto-lisp] lisp reading list
by Paul Tarvydas 08 Jan '10

08 Jan '10

At the end of this month's meeting, Justin asked what are some of the seminal lisp books to bring on a long trip. I found that I was unable to immediately answer the question. After pondering this on the way home, I realized that I didn't learn lisp from books - I learned it by reading source code of implementations of lisp. In addition to this, good lispery doesn't necessarily come from learning lisp. It also comes from being a generalist - learning as many paradigms as possible, then using lisp as the vessel for combining those paradigms. (One of the more extreme examples of using lisp as a vessel might be SICP - the Structured Interpretation of Classical Mechanics, Sussman and Wisdom, http://mitpress.mit.edu/SICM/) Here's a brief summary of what I read / did: - played with writing assembler code for Z80's and MC6809's - read source code for Tiny Basic (Dr. Dobb's Journal of Computer Calisthenics and Orthodontia, http://en.wikipedia.org/wiki/Tiny_BASIC) - read source code for Utah Lisp (IBM 360). - read source code for Fritz van der Wateren's MC6800 Lisp and transcribed it to run on a Z80. - read Lisp 1.5 Manual http://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Program… - read John R. Allen's "Anatomy of Lisp" (a book) and implemented the lisp compiler contained in it on the Z80 lisp (fixing a few bugs in the book). It ran in 22K of RAM and successfully compiled the IOTA function to Z80 machine code. - learned how to build compilers by reading the source code to Small C (it became my 4th year EE thesis project - I rewrote the whole thing using "better" compiler techniques and got it to self-compile). http://en.wikipedia.org/wiki/Small_C - learned how multi-tasking works by reading Ric Holt's small, but wonderful books on the subject, the most up-to-date one being, I think, "Concurrent Euclid, Unix and Tunis". - read source code for V7 Unix (which is now published in book form, with a front cover illustration of students making clandestine copies of the source on a xerox machine, heh, heh). - read source code for Tunis. - (I only recently read the Smalltalk Blue Book http://web.archive.org/web/20070927190722/http://users.ipa.net/~dwighth/sma… - it is clearly an inspired work). - read papers on Orthogonal Code Generation (Cordy, et al) and Fraser-Davidson compilation techniques (long before gnu-c existed, gcc uses Fraser-Davidson RTL as its core). - read source code for PT Pascal, Tiny Pascal, Concurrent Euclid, S/SL, etc. - read and implemented the WAM tutorial http://web.archive.org/web/20030213072337/http://www.vanx.org/archive/wam/w… (I wrote the WAM in CL, but haven't finished debugging it yet). As I look at the list above, I note that most of the implementations I read were done on "simple" hardware (no mmus, pipelining, security rings, mmap'ed files, etc). This made the material accessible, readable, understandable, and brief. Understanding compilers helped me understand macros, since CL macros are similar to having a language with YACC built into it. So, another suggestion for reading up on lisp, is to read the source code for some of the simple lisp and non-lisp "classics", and then to spiral into lisp. (I can't vouch for it since I haven't done so, but maybe some of the open-source CL's would make good reading, too). pt ps. If anyone wants the source for Frits van der Wateren's lisp, I'm hoping to scan it in and post it on my site (I have his permission). At one point I was toying with the idea of bringing it back to life by writing a 6800 simulator (in CL). pps. If there is sufficient interest, I could bring and explain the (assembler) source of FvdW lisp to one of the meetings. It would be a quick and easy intro to assembler and to low-level lisp structures.

1 0