From: Laurence Withers Newsgroups: comp.os.msdos.djgpp Subject: Re: The DXE mechanism - has anybody used it effectively? Date: Sun, 27 Dec 1998 21:34:39 +0000 Organization: IP Message-ID: References: <199812272109 DOT QAA06917 AT envy DOT delorie DOT com> NNTP-Posting-Host: lwithers.demon.co.uk X-NNTP-Posting-Host: lwithers.demon.co.uk:194.222.80.1 X-Trace: news.demon.co.uk 914796644 nnrp-10:13901 NO-IDENT lwithers.demon.co.uk:194.222.80.1 X-Complaints-To: abuse AT demon DOT net MIME-Version: 1.0 X-Newsreader: Turnpike (32) Version 4.00 Lines: 33 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com --- Original Message --- From: DJ Delorie Time: Sun, 27 Dec 1998, 16:09:20 [snip] >sys/dxe.h needs `` extern "C" { } '' around the _dxe_load() >declarataion. DJGPP 2.02 has this. Did you remember to include > ? I did remember the include file (note lack of 'implicit declaration' warning). [snip] >Are you using DJGPP 2.01? 2.02 allows DXEs to have exceptions, >although I doubt they'd work right as there's no mechanism to chain >them back to the main application. DXEs are pretty simple. Perhaps >you want the GNU dld package? I am using 2.01; I will download the new version later (when all the new Christmas users have finished playing :-/ ). Exception support is a great bonus (my code is much neater and less error-prone due to using try{} and catch(){} constructs) - although, as you say, it won't 'cross the link' between DXE and EXE. This isn't a problem due to the way DXEs are used; if the DXE falls over, the EXE is going to fall over anyway - who cares that I can only return a char *? I don't suppose that ctors/dtors in global objects work in 2.02? Well, thanks for taking some time to explain this to me. Bye for now, -- Laurence Withers, mailto:lwithers AT lwithers DOT demon DOT co DOT uk Integrated Peripherals Operating System Project Leader || OPES Project Projects' homepage is at: http://www.lwithers.demon.co.uk/ Leader