On Wed, 9 May 2001, Dan Sugalski wrote: > At 09:33 AM 5/9/2001 -0700, Larry Wall wrote: > > >I think that's silly. You misuse a variable that requires an auto, the > >compile dies, that's all. And macros can be very useful for an abstraction > >layer that intended to *hide* the implementation. Hoisting implementation > >details into the name defeats that abstraction. > > I really, *really* don't want to hide very much of the implementation > details at the C code level. We do that right now, and it makes for a > twisty maze of macros, all alike. And the resulting C code bears very > little resemblance to what's actually written. (I've seen size increases of > two orders of magnitude--20 characters of source text become 2K or more > after macro expansion) But isn't that the whole point of macros? Who wants to see the same 2K of code at the top of every function? Cheers, -Ben -- Benjamin Sugars <[EMAIL PROTECTED]>
- Re: PDD: Conventions and Guidelines for Perl Source Code Dave Mitchell
- Re: PDD: Conventions and Guidelines for Perl Source... Alan Burlison
- Re: PDD: Conventions and Guidelines for Perl Source Code Larry Wall
- Re: PDD: Conventions and Guidelines for Perl Source... Jarkko Hietaniemi
- Re: PDD: Conventions and Guidelines for Perl Source... Larry Wall
- Re: PDD: Conventions and Guidelines for Perl Source Code Dave Mitchell
- Re: PDD: Conventions and Guidelines for Perl Source Code Larry Wall
- Re: PDD: Conventions and Guidelines for Perl Source Code Dan Sugalski
- Re: PDD: Conventions and Guidelines for Perl Source Code Dan Sugalski
- Re: PDD: Conventions and Guidelines for Perl Source... Jarkko Hietaniemi
- Re: PDD: Conventions and Guidelines for Perl Source Code Benjamin Sugars
- Re: PDD: Conventions and Guidelines for Perl Source Code Alan Burlison
- Re: PDD: Conventions and Guidelines for Perl Source... Nick Ing-Simmons
- Re: PDD: Conventions and Guidelines for Perl Source Code Dave Mitchell
- Re: PDD: Conventions and Guidelines for Perl Source Code Dave Storrs