| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | How is memory handled? |
NH> My concept of localization requires the use of a string table. NH> The impression I got was that sharable resources are slower to NH> load and execute than their counterpart (strings written into NH> source code). MB> It is my impression, that string lookups are more flexible MB> than loadable shared resources, ie. one can change the localisation MB> at runtime, whereas those shared resources are "hardwired". Or am I MB> getting something wrong. Now I'm confused. I was under the impression that string lookups could occur with equal facility in both source code and shared resources. þ CMPQwk 1.42 999 --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 1 379/1 633/267 |
|
| 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™.