| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Memory blocks snuffe |
G'Day Michael,
-=> Quoting Michael Stapleton to Frank Adam <=-
MS> You can't make many assumptions about how an OS handles memory.
FA> Yeah, oh well it was a good idea while it lasted. Perhaps 4-5
FA> pages of #ifs would do it.:)
MS> It's still a good idea, and I don't think it'd take too many pages
MS> of #ifs to cover a large number of compilers & OSs. Still, it would
MS> be a nasty job for one person; I expect that it would be simpler if
MS> each section was written by someone who is expert in that
MS> compiler/OS.
Damn, that leaves me right out of it.:)
MS> Actually, (if memory serves me correctly) your routines wouldn't
MS> require much modification to work properly on the Amiga. OTOH, I
MS> only use the malloc() family routines when I'm writing portable
MS> code, since I normally use the AmigaOS AllocMem() function for
Borland does have allocmem() and it's highly portable too..
As long as you're on a DOS platform and in Borland :-)
MS> Amiga-specific programs. FWIW, we also have a cute function called
MS> AllocEntry(), which allocates several blocks at once, using a linked
Don't have this one, i'm not really sure what that would be good for,
multiple arrays perhaps ?
L8r Frank (fadam{at}ozemail.com.au).
___ Blue Wave/DOS v2.21
--- Maximus 3.01
* Origin: The Software Parlour (3:635/544)SEEN-BY: 50/99 620/243 623/630 632/349 635/503 544 727 711/401 409 410 413 SEEN-BY: 711/430 808 809 932 934 712/515 713/888 714/906 800/1 @PATH: 635/544 50/99 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.