This is the mail archive of the archer@sourceware.org mailing list for the Archer project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Frames as scopes

From: "Jim Blandy" <jimb at red-bean dot com>
To: "Tom Tromey" <tromey at redhat dot com>
Cc: "Doug Evans" <dje at google dot com>, archer at sourceware dot org
Date: Tue, 6 Jan 2009 10:56:56 -0800
Subject: Re: Frames as scopes
References: <8f2776cb0812301357m6aebb269t2c228e378c58a37c@mail.gmail.com> <e394668d0901010847o4d02126dx439cd4c1857b050a@mail.gmail.com> <8f2776cb0901021758s64248813nd6dfd59c91806fc0@mail.gmail.com> <m37i59i9fd.fsf@fleche.redhat.com>

On Mon, Jan 5, 2009 at 4:07 PM, Tom Tromey <tromey@redhat.com> wrote:
> I don't think there's a deep reason to prefer one or the other.  There
> are plenty of examples of successful projects using either.  I just
> tend to prefer not having a separate thin, low-level API that must be
> explained as well.

Fewer things to explain is always good.

Part of the reason I'd segregate the primitives into their own module
would be to make it easier to say, "We don't explain this."  (This
would have to be accompanied by a practice of providing public
functionality that covers everything the primitives do, so that the
primitives are indeed uninteresting.)

References:
- Re: Frames as scopes
  - From: Doug Evans
- Re: Frames as scopes
  - From: Jim Blandy
- Re: Frames as scopes
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]