macro FAQ

[eltronic at juno.com]

On 24 Aug 2003 16:43:42 +0200 Jacek Generowicz <jacek.generowicz at cern.ch>
writes:
> As I've said repeatedly:
true

> - I do _not_ necessarily advocate the inclusion of macros in 
> Python.
grain of salt?

> - I merely wish to dispel the myth that macros make code less
>   readable[*]: they _ease_ understanding of the code.

maybe with 'a few' simple macros. the fear, if any, is that imported
files depending on more macros will eventually be too great to fit your
brain. its a decision many agree with and has been amply fleshed out with
all sides represented. 
we would all use them, debug them, curse them often.
macros containing macros will be possible. 
with latent bugs and  security holes now multiplied.
they can solve nothing useful speedwise since they wont replace code
inline. with lazy evaluation of code this is less of a concern.

> 
> [*] And they don't fragment languages either.
I'm betting you usually get the last word.

macros [will/might/beyond all doubt can] fragment the language into
harder to read pieces. not the origional argument, but a concern.
if everyone shoots for 100% of their personal truth the FAQ will be
unreadable. 

keep it to at most few short paragraphs please.


e
please forward all spam  to "not my real email"<help at ftc.gov>

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!