[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: do-nothing macro generates nil nevertheless
- To: info-mcl@digitool.com
- Subject: Re: do-nothing macro generates nil nevertheless
- From: yost@rclsgi.eng.ohio-state.edu (Dave Yost)
- Date: 27 Feb 1995 03:25:14 GMT
- Organization: Dave Yost's house
- References: <3iqno7$mab@news.internex.net>, <gat-260295131710@milo.jpl.nasa.gov>
- Sender: owner-info-mcl@digitool.com
In article <gat-260295131710@milo.jpl.nasa.gov>,
Erann Gat <gat@robotics.jpl.nasa.gov> wrote:
>In article <3iqno7$mab@news.internex.net>, yost@rclsgi.eng.ohio-state.edu
>(Dave Yost) wrote:
>
>>I've been implementing some debug macros that only
>generate code depending on what's in *features*.
>
>The proper way to do this is to use the #+ read macro, e.g.:
>
>(progn
> 3
> #+debug(do-debugging-stuff))
There should be a way to make a macro that can be as transparent
as #+ is when its symbol is not in *features*.
That's what I should have said.
Dave Yost
@ .com