From: "Eric M. Ludlam" <ericludlam@gmail.com>
To: David Engster <deng@randomsample.de>
Cc: 10781@debbugs.gnu.org
Subject: bug#10781: EIEIO namespace use
Date: Sat, 28 Apr 2012 18:29:44 -0400 [thread overview]
Message-ID: <4F9C6F58.7070803@siege-engine.com> (raw)
In-Reply-To: <87sjfnh8lv.fsf@engster.org>
On 04/28/2012 05:03 PM, David Engster wrote:
> Stefan Monnier writes:
>>> Yes, I think 'this' should indeed become 'eieio-this'. It will also be
>>> the most work, since at least in CEDET you *very* often have
>>
>>> (defmethod foo ((this someclass) ...)
>>> ...)
>>
>>> so a 'this' in such a method is perfectly fine.
>>
>> An alternative approach is to keep the name `this' but get rid of the
>> global definition. I.e. Either completely remove the (defvar this nil),
>> or replace it with (defvar this).
>
> Eric, what would you prefer? I don't know enough about CLOS to say how
> important a global 'eieio-this' actually is. Either way, I just tested
> both solutions on CEDET trunk and each produced exactly this single
> compile warning:
>
> In ede-flush-directory-hash:
> files.el:230:38:Warning: reference to free variable `this'
>
> So actually, this appears to be a much smaller issue than I initially
> thought. It seems pretty much every 'this' in CEDET is already bound in
> the defmethod's argument list.
I would be happy to see 'this' just completely removed. It was put in
when I was mimicing C++, and some old programs of mine that have long
since rotted away depended on it. I'm actually surprised there was a
reference to it in CEDET still. That will be good to clean up.
Eric
next prev parent reply other threads:[~2012-04-28 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 18:39 bug#10781: EIEIO namespace use Stefan Monnier
2012-04-28 10:28 ` David Engster
2012-04-28 12:29 ` Eric M. Ludlam
2012-04-28 15:22 ` Stefan Monnier
2012-04-28 15:55 ` David Engster
2012-04-28 19:43 ` Stefan Monnier
2012-04-28 21:03 ` David Engster
2012-04-28 22:29 ` Eric M. Ludlam [this message]
2012-04-29 8:06 ` David Engster
2012-04-29 12:14 ` Eric Ludlam
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F9C6F58.7070803@siege-engine.com \
--to=ericludlam@gmail.com \
--cc=10781@debbugs.gnu.org \
--cc=deng@randomsample.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.