From: Stefan Monnier <monnier@iro.umontreal.ca>
To: ian martins <ianxm@jhu.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: ob-haxe
Date: Tue, 19 Jan 2021 23:01:06 -0500 [thread overview]
Message-ID: <jwvmtx46z53.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAC=rjb6x2grbeQjsQcWi2+EwOB5MCgh-aH=Pfc4Z+a19Kva_UA@mail.gmail.com> (ian martins's message of "Tue, 19 Jan 2021 22:25:49 -0500")
> That makes sense. Where there is shared code or variables it makes
> sense to keep the implementations together. For the ob-haxe and
> haxe-mode case the implementations are independent of each other.
That's inevitably the case, given that they were developed separately.
> I guess if haxe had a flymake integration it would want to share the
> compiler name variable with ob-haxe, though.
Yup, same thing if there was a REPL with an inferior-haxe-mode.
> Do you think it would be better to merge the packages or just add a
> dependency from haxe-mode to ob-haxe? Does it make a difference?
The difference is the ease with which the two parts can share code.
Stefan
next prev parent reply other threads:[~2021-01-20 4:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 12:48 [ELPA] New package: ob-haxe ian martins
2021-01-17 22:41 ` Stefan Monnier
2021-01-18 3:35 ` ian martins
2021-01-18 16:31 ` Stefan Monnier
2021-01-19 5:30 ` Richard Stallman
2021-01-19 14:19 ` Stefan Monnier
2021-01-19 14:28 ` ian martins
2021-01-19 15:15 ` Stefan Monnier
2021-01-20 3:25 ` ian martins
2021-01-20 4:01 ` Stefan Monnier [this message]
2021-01-18 6:27 ` ASSI
2021-01-18 16:32 ` 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=jwvmtx46z53.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ianxm@jhu.edu \
/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).