Re: Hey, what is all this 'off topic' posting?

On Sun, 04 Sep 2005 20:17:37 +0200, Frank Bemelman wrote:

> "Ken Smith" <kensmith@xxxxxxxxxxxxxxx> schreef in bericht
> news:dffcuq$8ll$4@xxxxxxxxxxxxxxxxx
>> In article <pan.2005.09.04.15.39.36.685094@xxxxxxxxxx>,
>> keith <krw@xxxxxxxxxx> wrote:
>> [...]
>> >> With asm you know you will need 10 times more time to deliver 1/10th
>> >> of the functionality.
>> >
>> >Only if you've never heard of a macro.
>>
>> You missed an obvious argument. I spend at least as much time on
>> designing the system as typing in code. If coding in C was infinitely
>> fast, it could only save me about half the time.
>
> Okay, but the design of the system does not much to do with
> the choice of the language. It's not that C coders don't
> design and start right away with an empty main().
>
> Asm macro's are (sort of) subroutines. If they are large
> and often used, they eat a lot of space as well. But they
> are a great help to avoid many silly coding errors.

Macros are far more than (even sort of) subroutines. They can do
conditional processing too. A few years back (when I was doign such
things) I had a set of x86 assmebler macros that would do PL/I-like
branch constructs (IF/THEN/ELSE, SELECT/WHEN in both forms, LOOP, UNTIL,
etc.). Assembler macros are *much* more than (sort of) subroutines. If
that's all you're using macros for, I can see why you don't much like ASM.

--
Keith

.

Relevant Pages

  • Re: HLA and embedded controllers
    ... it has to test the return code in order to pass that exception back ... routines that wind up getting called in the middle of the call sequence ... same way with my design. ... which is stronger than MASM's recusive macros. ...
    (alt.lang.asm)
  • Re: A question (confusion) about closure
    ... If not in the first place, emacs lisp code could have evolved if elisp ... more modern tool underneath would not be difficult, because the design ... If you already have implemented some OO patterns manually, ... macros if needed. ...
    (comp.lang.lisp)
  • Re: Reflections on a classic Lisp Paper
    ... relative to other mechanisms as the rather different macros ... of a functioning fexpr-based lisp. ... Fexprs is that they're applicable and have first-class runtime ... the rest of their design decisions. ...
    (comp.lang.lisp)
  • Re: To C.
    ... I thought you where going to design such an interface to allow ... Especially as faults in the design of the part of Luxasm ... of its type system -- any further use is controlled via macros. ... only a short step to add automated stack alignment and name ...
    (alt.lang.asm)
  • Re: Python syntax in Lisp and Scheme
    ... It's deeply frustrating to hear ... > No macros, tho, just groups of programmers. ... process some specialized language we may use roughly-traditional parser ... design chips, and particularly to foster cooperation in this design ...
    (comp.lang.lisp)