[comp.sys.amiga] Pattern Matching & documentatio

hamilton@uiucuxc.UUCP (12/10/86)

dpz@topaz says:
> Of course, now I've got to give my own idea.  Make a system call that
> given a wildcard will return the appropriate expansion.  You still
> have ease of wildcarding for the programmer, and yet also have
> consistency for the user.  No hacks, no muss, no fuss, and a lot less
> work for the OS, which only has to do expansion when asked to.

    it doesn't have to be a system call; a library routine (either kind)
will suffice.  take it one step further, and have 2 versions of your
c compiler startup code (?startup.o or c.o or whatever).

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton
ARPA:	hamilton%uiucuxc@a.cs.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uiucuxc@uiuc.csnet	Phone:	(217)333-8703
CIS:    [73047,544]			PLink: w hamilton

hamilton@uxc.cso.uiuc.edu (12/20/86)

carolyn@cbmvax says:
>    Well Matt, there is no magic document.  I wish there was.
>    What we have is the AmigaDOS source code.
> 
>    BCPL is a bit like C, and it is possible to decipher and even
> make changes to localized portions of the code.  But when you
> start to trace code that interfaces with the private global functions
> via run-time linking, you get stopped by tables of labels and vectors
> that specify numerical offsets into other tables that are built at  
> run time.  And if you manage to make it to the other side of the
> table because a corresponding label on the other side happens to
> have a similar name, you get stuck there because because that code
> starts loading registers with labels defined as offsets into the
> run-time table.  
> 
>    So, you can either pay Tim King to reveal the inner secrets, 
> or wait until someone here has time to decipher a very large and
> very complex program that jumps all over the place.

    or, you can send those sources to me and i'll write the magic
document for you :-)!  seriously, i've been analysing those "tables
of labels and vectors" from disassemblies of the kickstart, with at
least moderate success.  the hardest part has been guessing what
each module does, based on study of the assembler opcodes.  if i had
reasonably descriptive labels, half the job would be done!

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton
ARPA:	hamilton%uiucuxc@a.cs.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uiucuxc@uiuc.csnet	Phone:	(217)333-8703
CIS:    [73047,544]			PLink: w hamilton

wagner@utcs.UUCP (12/26/86)

Hire him!  Let Tim go ahead and make improvements to AmigaDOS.  Let Wayne
come along behind and document it.  Sounds like an unbeatable team!

Michael