reAd diZ..!

i caNt force sUmbody 2 lyK me..
i caNt coNvince sUmbody 2 bLieve Me & apprec8 mE..
i cAnt pLeased sUmbody 2 maKe frNdZ w/me..
i cAnt b perFect as waT dEy wAnt me 2 be..
i caNt say "STOP" 4 dos pipOl hu kiPs on juDging mE
neGatiVeLy & sAy "NO" 4 doS pipoL hU kiPs oN hurTing me..
i cAnt conTrol dosruMors & neGAtiv feEdbaCks rUshing oN me..
Bt 1 thing 4 xUr,,..
"I LUV doS trU frNdz hu Can aCCept me & lUv me 4

"WHO I AM" not 4 "WAT I AM"....

Monday, October 6, 2008

Question # 5:

Answer:

1.Macros

Many assemblers support macros, programmer-defined symbols that stand for some sequence of text lines. This sequence of text lines may include a sequence of instructions, or a sequence of data storage pseudo-ops. Once a macro has been defined using the appropriate pseudo-op, its name may be used in place of an mnemonic.
Macro assemblers often allow macros to take parameters. Some assemblers include quite sophisticated macro languages, incorporating such high-level language elements as optional parameters, symbolic variables, conditionals, string manipulation, and arithmetic operations, all usable during the execution of a given macros, and allowing macros to save context or exchange information. Thus a macro might generate a large number of assembly language instructions or data definitions, based on the macro arguments. This could be used to generate record-style data structures or "unrolled" loops, for example, or could generate entire algorithms based on complex parameters. An organization using assembly language that has been heavily extended using such a macro suite can be considered to be working in a higher-level language, since such programmers are not working with a computer's lowest-level conceptual elements.

http://en.wikipedia.org/wiki/Assembly_language#Assembly_language

No comments: