unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hugo Thunnissen <devel@hugot.nl>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New Package: phpinspect.el
Date: Tue, 15 Aug 2023 19:45:38 +0200	[thread overview]
Message-ID: <6c692fd7-24ba-be42-7c73-0cc950561479@hugot.nl> (raw)
In-Reply-To: <jwvsf8ouaov.fsf-monnier+emacs@gnu.org>


On 8/12/23 06:56, Stefan Monnier wrote:
>> I would like to propose my package, phpinspect.el, to be added to GNU Elpa.
> Done.
>
> AFAICT the code has currently some significant problems in terms of
> dependencies which make its compilation fail because variables are used
> by macros during compilation when the var has not yet been defined, or
> macros are used before they're defined, etc...
>
> The patch below seems to make the compilation go through (and fixes
> various warnings), but there are a lot of compilation warnings left
> which you might want to check.  It also includes a few FIXMEs.
>
>
>          Stefan
>
>

And here I was thinking that I had fixed all of the byte compilation 
problems.. Turns out it was only working because I byte compiled 
everything within the same emacs session. I made some changes and think 
things should be in order now. At least, the following shell script 
doesn't seem to result in any errors:

for file in ./*.el; do
     cask emacs -batch -L . --eval '(setq byte-compile-error-on-warn t)' 
-f batch-byte-compile "$file" || break
done

I see some warnings in your log that concern files in the "benchmark" 
and "test" directories. These files are not required for the package to 
function. Can these be excluded from the ELPA build somehow? I have seen 
some projects use a "lisp" directory for their source code, is that the 
recommended approach for this?


Thanks,

- Hugo





  parent reply	other threads:[~2023-08-15 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 20:22 [ELPA] New Package: phpinspect.el Hugo Thunnissen
2023-08-12  4:56 ` Stefan Monnier
2023-08-12  5:04   ` Stefan Monnier
2023-08-15 17:45   ` Hugo Thunnissen [this message]
2023-08-15 20:28     ` Philip Kaludercic
2023-08-15 21:33       ` Hugo Thunnissen
2023-08-15 21:56         ` Philip Kaludercic
2023-08-15 22:03     ` Stefan Monnier

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=6c692fd7-24ba-be42-7c73-0cc950561479@hugot.nl \
    --to=devel@hugot.nl \
    --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).