Calling all zasms

[David Given]

According to Google, there's a Z-machine assembler somewhere called zasm.
I want to do some hairy assembly, and Inform's assembler mode is as buggy
as a very buggy thing; as the zasm author seems to have moved to limbo and
taken its web site with it, does anyone happen to have a working copy
(with documentation) they could let me have?

--
+- David Given --------McQ-+ "The English people are like English beer. Froth
| Work: d...@tao-group.com | on top, dregs at the bottom, the middle excellent."
| Play: d...@cowlark.com | --- Voltaire
+- http://www.cowlark.com -+

[Brian C. Lane]

In article <nu5sh9...@127.0.0.1>, David Given wrote:
>According to Google, there's a Z-machine assembler somewhere called zasm.
>I want to do some hairy assembly, and Inform's assembler mode is as buggy
>as a very buggy thing; as the zasm author seems to have moved to limbo and
>taken its web site with it, does anyone happen to have a working copy
>(with documentation) they could let me have?

The only obvious one in the if-archive is one written in perl. It can be
found at:

ftp://ftp.guetech.org/if-archive/infocom/compilers/zasm

or any of your other favorite if-archive mirrors

Brian

--
Brian C. Lane - Linux Programmer/Consultant/Writer www.brianlane.com
www.nexuscomputing.com
Liberty & Privacy 'zine Editor www.libertynews.org
============================================================================
Of all tyrannies, a tyranny exercised for the good of its victims may
be the most oppressive. It may be better to live under robber barons
than under omnipotent moral busybodies. The robber baron's cruelty may
sometimes sleep, his cupidity may at some point be satiated; but those
who torment us for our own good will torment us without end, for they
do so with the approval of their consciences.
-- C. S. Lewis

[David Given]

In article <9A03E64E152BCA8E.CEE54606...@lp.airnews.net>,

br...@kermit.nexuscomputing.com (Brian C. Lane) writes:
> In article <nu5sh9...@127.0.0.1>, David Given wrote:
>>According to Google, there's a Z-machine assembler somewhere called zasm.
>>I want to do some hairy assembly, and Inform's assembler mode is as buggy
>>as a very buggy thing; as the zasm author seems to have moved to limbo and
>>taken its web site with it, does anyone happen to have a working copy
>>(with documentation) they could let me have?
>
> The only obvious one in the if-archive is one written in perl. It can be
> found at:

That's the one. In fact, the author contacted me after I sent the original
message, sent me a copy, and uploaded it, and I forgot to tell anyone.
[slaps wrist]

Unfortunately, the documentation has been lost, so if anyone happens to
have a copy lying around...

--
+- David Given --------McQ-+ Q. How much wood would a woodchuck chuck if a
| Work: d...@tao-group.com | woodchuck could chuck wood?
| Play: d...@cowlark.com | A. A woodchuck that could chuck wood would chuck as
+- http://www.cowlark.com -+ much wood as a woodchuck would.

[John Colagioia]

David Given wrote:

> In article <9A03E64E152BCA8E.CEE54606...@lp.airnews.net>,
> br...@kermit.nexuscomputing.com (Brian C. Lane) writes:
> > In article <nu5sh9...@127.0.0.1>, David Given wrote:
> >>According to Google, there's a Z-machine assembler somewhere called zasm.
> >>I want to do some hairy assembly, and Inform's assembler mode is as buggy
> >>as a very buggy thing; as the zasm author seems to have moved to limbo and
> >>taken its web site with it, does anyone happen to have a working copy
> >>(with documentation) they could let me have?
> > The only obvious one in the if-archive is one written in perl. It can be
> > found at:
> That's the one. In fact, the author contacted me after I sent the original
> message, sent me a copy, and uploaded it, and I forgot to tell anyone.
> [slaps wrist]
> Unfortunately, the documentation has been lost, so if anyone happens to
> have a copy lying around...

I don't have any documentation for it, but I do have a...uhm...well, it's not a
working source, per se, yet. It was, when it was a single routine, but breaking out
the second routine seems to have broken it. It does assemble clean, though, which
is a good starting point--in fact, chances are, I'm simply not using the correct
CALL opcode. The single-routine version, of course, is easily reconstructed from
this...

routine Hello
print "Hello, World!"
print_char 13
rtrue

routine _start
call_1n Hello
quit

That's as far as I got before getting dragged away to another whim-based
project...and I seem to have "broken" PERL, since zasm gives me grief when I try to
use it now, too...