Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!vsi1!wyse!mips!prls!pyramid!oliveb!amiga!jimm From: jimm@amiga.UUCP (Jim Mackraz) Newsgroups: comp.sys.amiga.tech Subject: Re: CloseFonts() problems Message-ID: <3230@amiga.UUCP> Date: 2 Jan 89 19:33:14 GMT References: <3599@tekig5.PEN.TEK.COM> <10097@well.UUCP> <14355@oberon.USC.EDU> <3226@amiga.UUCP> <14370@oberon.USC.EDU> Reply-To: jimm@cloyd.UUCP (Jim Mackraz) Organization: Commodore-Amiga Inc, Los Gatos CA Lines: 48 In article <14370@oberon.USC.EDU> papa@pollux.usc.edu (Marco Papa) writes: )In article <3226@amiga.UUCP| jimm@cloyd.UUCP (Jim Mackraz) writes: )|Hold on, here, fellas. Is there a real reason to flush the font? This thread )|started when some guy thought the memory for an unused font was unavailable. )|This isn't so that your customers feel that you've returned all your memory, )|is it? Or maybe to satisfy the BKDC rules or something. )That's definitely THE main reason most third parties do the HUGE AllocMem, )as the last thing before closing shop. Then we have identified a Point of Education. Maybe something like 'flushlibs' should be included in a standard Workbench menu (and in System: ?) so that we can cater to people's psychological problems. ;^) At very least, amend the BKDC rules to say that you must return memory after a manual purge is run. )|Problems I'm aware of include: )|1) Expunge should walk the device/libs lists in reverse order so that if one )| library is opened by another, the opener hears the expunge first. )| (discovered by Bill Hawes, the little genius). )|2) Expunging should terminate when it gets enough memory for the AllocMem. )|3) Some device (serial maybe) hangs onto resources until it is expunged, so )| expunging it is the only way to get the resources back (this would be a )| bug in the device). )Are these bugs still present in 1.3? In they are, why weren't fixes included )in SetPatch if, as it seems from your comments, these are all known bugs? Come again, Marco? All known bugs must be fixed in 1.3 or SetPatch? That's not realistic, and it makes me disinclined to mention known problems even in this developer-oriented forum. I learned most of these on BIX, myself. No, all of them. See you there. )|If I'm missing something here, I'd be pleased to be educated. )No, you're not missing anything. Bu from now on consider that, as I said, the )practice is widespread. Well, we've identified that *someone* needs education, and I suppose that includes the users. I'll forward the suggestion to cbmvax!bugs, with the words "Enhancement" and "documentation" in the subject line. )-- Marco Papa 'Doc' jimm