Acl 4.3 and CM

[Lawrence Troxler]

On Tue, 21 Jan 1997, Matti J Koskinen wrote:

> 
> Hi all
> 
> I received yesterday a copy of Allegro 4.3 for Linux and compiled Common
> Music with it. The compilation went without problems (only warnings about
> float-type) and the code looks like working ok. The next thing to do is to
> get the midi working. 
> I have tclmidi-3.1f, which can read midi
> from keyboard and to integrate mrec and mplay shouldn't be very
> complicated 

Hi Matti. I just recently set up linux on my machine and installed ACL.
Regarding MIDI, I'm still a Linux novice, but I wonder why you need
something like tclmidi? Can't you just read and write raw midi data to
/dev/midi0x?. Of course this won't handle scheduling tho. What about the
/dev/sequencer device, however? I can't find any documentation on it, but
I imagine that it might schedule output. I plan on taking a look at the
Jazz sequencer source to try to figure out how this works (assuming of
course, that Jazz is under GPL license, and using /dev/sequencer).

> A rather
> interesting point is that the compilation with my 486-33 DX took almost an
> hour while compiling with clisp it took only just about 15 mins. The code
> generated with acl is about 4.5 megs and it is not a loadable module as in
> clisp but an executable module with all the common lisp features.
> 
"Interesting" is the wrong word, IMO. This is a rather *disturbing* point.
I
had assumed that Allegro would be better than CLISP (which I was using on
DOS), but now I wonder which is really better. Take a look at the ACL
installation guide for some horror stories about sizes on different
platforms. Hopefully, ACL will make up for it in speed of executing
compiled code. 

Larry Troxler
lt@westnet.com