From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Defvar not called at top level Date: Wed, 24 Nov 2021 08:38:22 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36375"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 24 14:44:10 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mpsZG-0009Ed-5k for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Nov 2021 14:44:10 +0100 Original-Received: from localhost ([::1]:33942 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mpsZF-0002e1-3v for ged-emacs-devel@m.gmane-mx.org; Wed, 24 Nov 2021 08:44:09 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48668) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mpsTw-00024D-Qp for emacs-devel@gnu.org; Wed, 24 Nov 2021 08:38:44 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:17131) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mpsTp-00028y-0y for emacs-devel@gnu.org; Wed, 24 Nov 2021 08:38:39 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D26654409A6; Wed, 24 Nov 2021 08:38:30 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 5475F440962; Wed, 24 Nov 2021 08:38:29 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1637761109; bh=NDhUzTfduIB1t4Xkdobncz4FOAJXj5ttkTzLe2P4hMA=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=HQuVazFLkUBhRj7UHtUYoi+lkSUDtxBXbaD3jpFagFNrDSWQzbSChO27wVQnx/w4P +h5GlBT97tWHI55uRDk8NMmmTRAQYq4TBIsCSYZYSG0o+w7GzviVXIWdNhV7f3I+VB Ut5ztGGQyADzsfENWu2IYT3GR96fpha3ZLK72hMuLT/QxPW5kqFFgREmfU4s2qcEWn +LEGRvIHEjv3xQdjiMnGBRC/M1/I2KSgv2Q1jHwFtx1paWSTbTMCuHgzq7d6/PQjxQ 3ho7ousLL+9HwWCPg307wYhyJ6F8wtyHzk5SCvVZO0OrFwR5h5Bed42RpmGQ0OgW8B Go2M52rm52O5Q== Original-Received: from pastel (unknown [216.154.30.173]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 10B1612089F; Wed, 24 Nov 2021 08:38:29 -0500 (EST) In-Reply-To: (Arthur Miller's message of "Wed, 24 Nov 2021 11:47:16 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:279994 Archived-At: Arthur Miller [2021-11-24 11:47:16] wrote: > Stefan Monnier writes: >> Arthur Miller [2021-11-23 14:28:04] wrote: >>> Just a question: why is it important to call defvar from top level? >>> I would like to have some code that generates some other code, amongs that to >>> declare few global symbols with auto generated docs as well. >> >> Presumably you can do this with >> >> (defmacro FOO (..) ... `(defvar ...) ...) >> >> (FOO ...) >> >>> If I call those from a defun/macro normally I get that warning that defvar is >>> not called at top level; >> >> Can you show the actual warning? > > > Thank you for the answer; it seems like I can't :). > > I am sorry, I had too many things in my head and confused things. It was not > "defvar" it was "defvar-local". I appologize. So the warning was not about `defvar` but about `make-variable-buffer-local`. The reason for this warning is to catch the widespread confusion between `make-variable-buffer-local` and `make-local-variable`. Stefan