Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	       Mark Kettenis	<mark.kettenis@xs4all.nl>,
	<thomas@codesourcery.com>,        <gdb-patches@sourceware.org>,
	<kevinb@redhat.com>
Subject: Re: [SH] regs command
Date: Thu, 24 May 2012 18:05:00 -0000	[thread overview]
Message-ID: <87k4018ng4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1205220019270.11227@tp.orcam.me.uk> (Maciej	W. Rozycki's message of "Tue, 22 May 2012 00:36:13 +0100")

>>>>> "Maciej" == Maciej W Rozycki <macro@codesourcery.com> writes:

Maciej>  Hmm, I gave it some thinking and it looks to me like a
Maciej> functional programming problem to solve (e.g. AC_REQUIRE in
Maciej> autoconf-speak; I didn't really do any functional programming
Maciej> beyond that).

:)

Maciej> This may not be possible to express in C in a very elegant way,
Maciej> but I can imagine retaining the current init.c
Maciej> arrangement/scriptery, but in addition to that letting
Maciej> initialisers call one another.

Another way would be to just directly express it, say in comments that
are extracted by the script used to create init.c.

    /* Requires: something_else */
    void
    _initialize_something (void) { ... }

Then dependency loops could be caught at init.c-generation time.

The problem with anything like this is maintenance of the dependencies.
That is, how do you know if one is stale?  Or what do you do if you
actually hit a cycle?

For example, in the case in question -- when we eventually remove the
"regs" command, would we remember to delete the "Requires"?

Tom


  reply	other threads:[~2012-05-24 18:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:56 Thomas Schwinge
2012-05-16 14:26 ` Joel Brobecker
2012-05-16 16:32   ` Thomas Schwinge
2012-05-16 16:58     ` Joel Brobecker
2012-05-16 17:21       ` Thomas Schwinge
2012-05-16 18:47         ` Tom Tromey
2012-05-16 19:06           ` Joel Brobecker
2012-05-16 19:38             ` Maciej W. Rozycki
2012-05-17  0:59               ` Maciej W. Rozycki
2012-05-17 11:10                 ` Mark Kettenis
2012-05-17 11:23                   ` Maciej W. Rozycki
2012-05-17 12:38                     ` Joel Brobecker
2012-05-17 15:23                       ` Mark Kettenis
2012-05-17 15:45                         ` Joel Brobecker
2012-05-17 19:52                           ` Tom Tromey
2012-05-17 20:38                             ` Joel Brobecker
2012-05-18 12:23                               ` Maciej W. Rozycki
2012-05-18 12:39                                 ` Pedro Alves
2012-05-18 12:49                                   ` Joel Brobecker
2012-05-18 13:33                                     ` Pedro Alves
2012-05-18 13:47                                 ` Tom Tromey
2012-05-21 23:36                                   ` Maciej W. Rozycki
2012-05-24 18:05                                     ` Tom Tromey [this message]
2012-05-17 19:32         ` Kevin Buettner
2012-05-16 18:36       ` Tom Tromey
2012-05-16 18:36     ` Pedro Alves
2012-05-16 19:36     ` Eli Zaretskii
2012-06-06 18:10     ` Thomas Schwinge
2012-08-10  9:22       ` Thomas Schwinge
2012-08-10 16:20         ` Tom Tromey

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=87k4018ng4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=macro@codesourcery.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=thomas@codesourcery.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox