Re: A challenge for RosAsm
- From: Betov <betov@xxxxxxx>
- Date: 30 Jun 2005 10:07:18 GMT
"wolfgang kern" <nowhere@xxxxxxxxxxx> écrivait news:d9up1d$oqq$2
@newsreader1.utanet.at:
>
> My opinion about Macros:
>
> * + reduces source size
> - on cost of 'direct readability'
> - bloats the .exe (in hidden form)
> * + minor convenience for lazy programmers
> * - any change in it will affect many program parts.
>
> So if I need several similar code parts, I either
> write one routine which cover all wanted variations, or
> I just copy/paste and modify as desired.
> And I never would hide any code block, as parts and trails
> often can be used more than one time, so I must see it.
It depends of what kind of Macro. I mean, on what the
Macro Purpose is.
To me, the HLL Macros should be used, mainly, for HLL-
Like Constructs. This is the purpose where they are the
most helpfull, because they increase the readability,
with out hidding much, as long as everybody immidiately
guess what a 'If", a "While", a "Loop_Until", and so
one... do and are.
For the other Macros, like the OOP ones, they effectively
hide a bit too much, IMHO, and, whereas they may be of
real help for the developer, they may be a bit painfull
for the external reader.
In between... taste...
;)
Betov.
< http:/rosasm.org >
.
- References:
- A challenge for RosAsm
- From: Randall Hyde
- Re: A challenge for RosAsm
- From: Betov
- Re: A challenge for RosAsm
- From: Randall Hyde
- Re: A challenge for RosAsm
- From: Betov
- Re: A challenge for RosAsm
- From: Randall Hyde
- Re: A challenge for RosAsm
- From: wolfgang kern
- A challenge for RosAsm
- Prev by Date: Re: Click...
- Next by Date: Re: A challenge for RosAsm
- Previous by thread: Re: A challenge for RosAsm
- Next by thread: Click...
- Index(es):
Relevant Pages
|