[chuck-users] code reusability

mike clemow michaelclemow at gmail.com
Tue Jun 15 17:58:19 EDT 2010

Okay folks,

It's hacky and slow, but it does technically work (on my Mac with Snow

how to:

1) make sure chuck is installed ;)
2) unzip the archive, open a terminal window
3) cd /path/to/chuck-session-handler_v01
4) python csh-v1r0.py - notice that the script starts chuck and adds the
setup.ck and mylib.ck files
5) open another terminal window
6) in that terminal window cd /path/to/chuck-session-handler_v01
7) chuck + test.ck
8) verify that the output (in the first window) prints "5 :(int)"
9) killall chuck
10) notice that the script reboots chuck and adds the setup.ck and mylib.ckfiles
11) chuck + test.ck
12) verify that the output (in the first window) prints "5 :(int)"
13) rinse, repeat...

Questions, comments, concerns?  I think that something like this could be
very interesting as part of an incremental programming system that would
keep track of the classes that were written and add them to the list of
classes that are included in setup.ck.  I think that this would be
interesting for building and maintaining libraries for live-coding.

Anyway, it's a start... of something.


On Tue, Jun 15, 2010 at 2:57 PM, mike clemow <michaelclemow at gmail.com>wrote:

> > By the way: good programmers enforce legible code, not languages. :)
> Yes, Joe, but if *I* write it in Perl, it will be crap code.  :)
> I'm working on a Python stub application for this session handler idea.  We
> can use it as a basis and build on it, if you guys like it.  What Andrew and
> I were talking about doing is actually quite different than what Scott
> Wheeler's original Perl script did.  I'm much more interested in the session
> handler idea, but I'm sure there's a way to combine them.  I personally
> don't think it makes much difference what language they two are written in
> as long as they play nice together.
> Mike
> On Sat, Jun 12, 2010 at 10:29 PM, Joe McMahon <mcmahon at ibiblio.org> wrote:
>> 2010/6/12 mike clemow <michaelclemow at gmail.com>:
>> > I would be happy to help make something too, although I would say we
>> should
>> > use Python for two reasons:
>> > 1) I know Python much better than Perl.
>> > 2) Python enforces much more legible code.
>> Okay, well, I'll take a look at the Perl version; let's see what we
>> can come up with.
>> By the way: good programmers enforce legible code, not languages. :)
>> Programming languages can help out, but it's possible to write crap
>> code in any language. Having written both, I think that writing good
>> Perl does indeed require more discipline, but the power advantages
>> (especially CPAN) help a lot.
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
> --
> http://michaelclemow.com
> http://semiotech.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20100615/4e4d1d7a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: chuck-session-handler_v01.zip
Type: application/zip
Size: 1421 bytes
Desc: not available
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20100615/4e4d1d7a/attachment.zip>

More information about the chuck-users mailing list