Fri 2003-02-07 10:47, Neil Heller (1:106/2000) wrote to andrew clarke:

ac> You can have string tables (and icons, bitmaps, etc.) which can 
ac> be shared by multiple instances if they are marked 
ac> "sharable". I don't think this applies to strings within 
ac> the source code though (but I suppose in theory it could, 
ac> but might slow things down a lot).

NH> Is that common in the case of shared executables?

ac> Yep.  It also makes localisation easier.

NH> Please tell me if I am experiencing a misunderstanding.

NH> My concept of localization requires the use of a string table.  The 
NH> impression I got was that sharable resources are slower to load and 
NH> execute than their counterpart (strings written into source code). 

If the strings were loaded on demand then this would seem to me to be
slower than loading them all at once at executable startup (even if they
weren't going to be used).  I guess whether this is acceptable depends on
the application.

But when I made that comment I was really thinking in terms of compliation
time. If a Windows compiler had to translate all the strings from the
source code into a string table resource, then bind the string table on to
the executable after the code was compiled, it might be quite slow.  And
the compiler would also have to somehow automatically map the bound string
table so its strings could be transparently used by the program.

-- mail{at}ozzmosis.com

--- timEd/Cygwin 1.11.a4