Re: cc-vars.el

[Miles Bader <miles@lsi.nec.co.jp>]

Martin Stjernholm <mast@lysator.liu.se> writes:
> > /.../  A few extra fboundp checks at load-time are so utterly
> > inconsequential that it's hardly worth worrying about the possibility that
> > they might be generated in some cases.
> 
> What makes you think they are restricted to load time code?

The idioms I'm thinking of are:

  (if (fboundp 'foo)
      (foo bar)
    (foo-work-around bar))

which will work for `when' too, due to macroexpansion:

  (when (fboundp 'foo)
    ...do stuff...
    (foo bar)
    ...do more stuff...)

I'd probably make it work for `and' too, so you could do:

  (and (fboundp 'foo) (foo bar))

What case do you have in mind where these aren't sufficient?
Can you give examples?

> What would be the problem of adding a macro in the bytecomp
> environment to control the warning aspect only?  That has to be
> simpler than recognizing the if-form.  It's not like it's an either-or
> issue between two irreconcilable solutions.

No, but let's not add both unless it's actually necessary.

-Miles
-- 
Come now, if we were really planning to harm you, would we be waiting here, 
 beside the path, in the very darkest part of the forest?