Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,722 of 4,675    |
|    Alex McDonald to R.Wieser    |
|    Re: String literals in asm source code    |
|    31 Dec 18 17:29:54    |
      From: alex@nospicedham.rivadpm.com              On 31-Dec-18 12:53, R.Wieser wrote:       > Alex,       >       >> With all the messages buried in the source stream, managing them becomes       >> difficult at scale or if multiple target languages are to be supported.       >       > If an assembler can manage labels just fine over multiple sourcefiles,       > multiple non-overlapping segments and for structures and even can ceep track       > changes in emitted code because of opcode changes depending on the distance       > to the target label than I have no doubt that something simple as keeping       > track of a few "at use" declared static(!) strings will not be much of a       > problem either.              Perhaps I didn't make myself clear. The problem is the programmer's, not       the assembler's. The languages I mean are human ones.              >       >> Labels aren't text messages. There are several use cases for the =X       >> operand here.       >       > You're again jumping to a fully other language / environment and how it       > work(s|ed) there. Try to stay here, and with what the OP asked for.              You'll need to be clearer here. I'm not understanding how discussing the       the OP's assembler and its literal string =B feature is "jumping to a       fully other language".              >       >> labels don't in general need any management.       >       > As shown in the above, I think differently. In *general* they need quite a       > bit. Only in fringe cases they need none.              Generally I wouldn't expect to translate the labels from something to       English or Spanish or German or French when internationalising an app. I       would do that for the static text in the app.              Which is where we came in. Used sparingly, =B strings are fine. I       wouldn't use beyond a handful because it's more difficult to manage       inlined messages at scale.                     --       Alex              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca