unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 'Eli Zaretskii' <eliz@gnu.org>,
	Drew Adams <drew.adams@oracle.com>,
	emacs-devel@gnu.org
Subject: Re: policy, recommendations regarding `cl-*'
Date: Thu, 27 Sep 2012 00:04:18 +0200	[thread overview]
Message-ID: <87haqktp99.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwv4nmku0v3.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 26 Sep 2012 13:54:54 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

> There's a bug: at run time, CL will not be loaded, so cl-position
> won't exist.
> For cl-defsubst, that's not a problem, because it gets macroexpanded
> away during compilation, so it's not needed at run-time.
>
> IOW if you use CL functions, you need (require 'cl-lib) without wrapping
> it in eval-when-compile.

That's perfectly clear, thanks.

-- 
 Bastien



  reply	other threads:[~2012-09-26 22:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 20:31 policy, recommendations regarding `cl-*' Drew Adams
2012-09-25 21:01 ` Eli Zaretskii
2012-09-25 22:09   ` Drew Adams
2012-09-26  1:15     ` Stefan Monnier
2012-09-26  2:51       ` Drew Adams
2012-09-26  3:29         ` Stefan Monnier
2012-09-26  7:02           ` Bastien
2012-09-26 12:59             ` Stefan Monnier
2012-09-26 13:12               ` Bastien
2012-09-26 17:54                 ` Stefan Monnier
2012-09-26 22:04                   ` Bastien [this message]
2012-09-27 20:35                   ` Michael Welsh Duggan
2012-09-27 22:10                     ` Stefan Monnier
2012-09-29  4:15                       ` Michael Welsh Duggan
2012-09-26 14:11           ` Drew Adams
2012-09-26 19:44             ` Stefan Monnier
2012-09-26 20:13               ` Drew Adams
2012-09-26  7:42     ` Eli Zaretskii
2012-09-26 13:00       ` Stefan Monnier
2012-09-26 14:11       ` Drew Adams
2012-09-26 13:37     ` Jason Rumney
2012-09-25 21:03 ` Helmut Eller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87haqktp99.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).