Path: utzoo!attcan!uunet!super!udel!rochester!rutgers!ucsd!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: ARP-questions and more
Message-ID: <8808242356.AA26888@cory.Berkeley.EDU>
Date: 24 Aug 88 23:56:27 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 19

>What, exactly, is 'handler'-code?
>In Dmouse, for instance, Matt Dillon has 'extracted' the handler-code,
>but what is the benefit of that?

	Dmouse comes in two parts.  The 'Dmouse' executable and the
'dmouse-handler' which must go in L:.  The reason it is split up is
so that all the extra baggage needed to handle the command line, help
text, etc... is NOT made resident.  The 'Dmouse' executable sets up all
the structures, gives help, etc... then LoadSeg()s the 'dmouse-handler'
(leaving it in memory) and then exits.

	So the only thing that remains in memory is dmouse-handler, not
Dmouse the executable with all the option handling and help.

	There are other kinds of handlers.  For instance, a DOS device
like PIPE: and many others you see in the Mountlist reference handlers
in L: which do the 'meat' of the job.

				-Matt