From: Vinicius Jose Latorre <viniciusjl@ig.com.br>
Cc: emacs-devel@gnu.org
Subject: Re: printing.el again
Date: Wed, 17 Nov 2004 23:53:42 -0200 [thread overview]
Message-ID: <419C00A6.90905@ig.com.br> (raw)
In-Reply-To: <m1mzxiwpnz.fsf-monnier+emacs@gnu.org>
Stefan wrote:
>> Maybe this should be documented in Emacs Lisp Reference or in other
>> suitable info, probably Byte Compiler Users Guide. Also other
>> byte-compiler optimizations should be documented.
>
>
> Actually, I don't think optimizations should be particularly mentioned.
> The interesting part of optimizing (featurep 'xemacs) is that it
> eliminates
> spurious warnings. There are other ways to get the same effect, such as
> what is done with (if (fboundp 'foo) ...) where the test is not optimized
> away, but where warnings are selectively prevented.
>
> I think a chapter on "eliminating warnings" is in order to document
> the use of
> (featurep 'xemacs), (fboundp 'foo), (defvar foo), (with-no-warning
> ...), ...
Well, I think it's important to know the optimizations we can use or not
and when.
Does the byte-compiler try to optimize featurep in general or only the
pattern (featurep 'xemacs) is optimized?
That is, if I have a code which test (featurep 'some-package) and
some-package is not loaded, does the byte-compiler eliminate the code
associated with this test?
Vinicius
next prev parent reply other threads:[~2004-11-18 1:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 5:59 printing.el again Stefan
2004-11-14 15:29 ` Vinicius Jose Latorre
2004-11-14 19:20 ` Stefan Monnier
2004-11-15 20:03 ` Vinicius Jose Latorre
2004-11-15 20:47 ` Stefan Monnier
2004-11-16 0:55 ` Vinicius Jose Latorre
2004-11-16 1:29 ` Stefan
2004-11-16 1:36 ` Luc Teirlinck
2004-11-16 14:47 ` Ralf Angeli
2004-11-16 16:51 ` Stefan Monnier
2004-11-18 1:53 ` Vinicius Jose Latorre [this message]
2004-11-18 16:30 ` Stefan Monnier
2004-11-18 22:44 ` Vinicius Jose Latorre
2004-11-18 23:31 ` Stefan Monnier
2004-11-19 20:04 ` Richard Stallman
2004-11-17 5:03 ` Richard Stallman
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=419C00A6.90905@ig.com.br \
--to=viniciusjl@ig.com.br \
--cc=emacs-devel@gnu.org \
/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).