On Sat, 21 Aug 2010 17:56:41 -0600 Paul Gilmartin <[email protected]> wrote:
:>On Aug 21, 2010, at 16:44, john gilmore wrote: :>> The notion that "customers" cannot reasonably be deprived of literals suggests that what is in question is some fill-in-the-blanks situation. Such problems can be dealt with under the hood (bonnet), whether they be screen-input or macro keyword-parameter ones: query and note assembled lengths that are not multiples of two bytes and provide a properly placed, immediately following literal pool entry that makes up the difference. (Avoid reuse of the same one-byte literal: literal pools are purged.) :>This is a joke, right? How would the programmer pose such a :>"query"? Is there an operation to place an entry in the literal :>pool, other than coding an instruction to reference it and ORGing :>back over it? :>Hmmm... :> * The first segment contains all literal constants whose :> assembled lengths are a multiple of 16. :>(loc. cit.) :>So, =0C'a' goes in that segment, since 0 is a multiple of 16. Sadly there are those with only hammers in their toolkit, so to them everything looks like a nail. A simple assembler parameter to force all literals to a minimum halfword boundary is a simple solution. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
