>In other words, generalizations like this are just that:
>generalizations. If you are writing code, you should be very aware of
>how it will operate in its likely environment, and what the compiler is
>going to do with the code you write when it gets optimized.
Yes, so why bother making guidelines that will most likely confuse people
who are likely to get confused? If there's a guideline like that, a novice
user might do who knows what kinda crap ("oh, I got 1GB of RAM, so I guess
I'll just alloc to my hearts content, rather than waste 1000 cycles!").
And I specifically didn't pick on the example <G> :)
-Michael
_______________________________________________
Asterisk-Dev mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
