Xref: news-dnh.mv.net comp.os.msdos.djgpp:2426
Path: news-dnh.mv.net!mv!news.sprintlink.net!news.oz.net!news.worldcom.com!news.sesqui.net!rice!news!sandmann
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DXE multiple functions
Date: Thu, 05 Oct 1995 07:56:30 CDT
Organization: Rice University, Houston, Texas
Lines: 14
References: <44vrlp$ldd AT dub-news-svc-2 DOT compuserve DOT com> <450dah$etl AT huron DOT eel DOT ufl DOT edu>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: clio.rice.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> Just an idea, but for a DXE couldn't you have the "one function" return 
> pointers to other functions in the DXE? I haven't tried this, so it may 
> be poppycock, but it would seem to me that since the DXE would have to be 
> somewhat static to be loaded in memory... your "one DXE function" could 
> accept parameters and return pointers to other functions... or your DXE 
> return value could be a block of pointers to functions. I'll try it, if I 

Yes, this is was my plan for implementation of multiple functions.  I have
never written the full DOCS, sorry.  The return item doesn't have to be 
a function, it can be a data structure (for a driver header, for example,
or a vector of function entry points).

I did test many of these things in developing DXEs.  The real problem with
DXEs is they can't call some libc functions (like I/O).