There are better designs than allocating storage at the explicit address in most cases (fork being the primary exception).
If it's the case that Kees mentioned of having a shared block that is allocated on first use (assuming you have good serialization), then use name tokens instead. A hard-coded address could fail if something changes in your system to make that address no longer accessible. If you're browsing a lot of storage to display or search for something, then certainly don't allocate it which just wastes system resources and tells you nothing useful. This would be especially true for 64-bit storage that allocating and browsing large areas would end up backing a lot of memory than you'd really need. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
