Re: [Octal-dev] crash?

[Dave O'Toole]

Arthur Peters wrote:
> 
> I had the same thought, but if you look through engine_quux.c you'll
> find that all the opcodes (quux's. is this definition correct? I had
> never heard the term "quux") do is to print their name and
> operands. This was just a interim release. It does not actually work,
> yet. Thanks for trying to report the "bug", though. Hopefully, dto
> will have something for us to work with soon. ;-> Latter.

Yes, sorry about this! All the current release does is test the digraph
compiler and print out what it's doing (i am happy to report that its
topological sorts seem correct); when the opcodes are in place (they are
very simple) this mechanism will carry out the operations needed to
complete a single block of audio and ship it out to the sound card. I.e.
this is the heart of Octal, the inner loop, and it is built as a machine
accepting a list of instructions (compiled by a recursive algorithm that
examines the interconnected machines and figures out what to do.)  

This interim release was made so that people could look at the header
files and docs to see the changes to the API, as I needed to break one
or two things and I felt it was best to do it sooner rather than later.
It isn't playable quite yet, although the underneath stuff is getting
there...

Sorry about the term "quux", I couldn't think of a better name and I
wanted to start writing it :-). The name might change in the future.
(Quux is a variable name like foo, bar, baz, etc, just not as common.) 

By the way I have finished the documentation tool I was working on, I
will be putting it up on my home page soon. (It will probably also get
included in octal itself, it is quite short.) 

-- 
@@@ david o'toole
@@@ address@hidden
@@@ www.gnu.org/software/octal