From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: <brobecker@adacore.com>, <thomas@codesourcery.com>,
<tromey@redhat.com>, <gdb-patches@sourceware.org>,
<kevinb@redhat.com>
Subject: Re: [SH] regs command
Date: Thu, 17 May 2012 11:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1205171215290.11227@tp.orcam.me.uk> (raw)
In-Reply-To: <201205171109.q4HB9Ljc005742@glazunov.sibelius.xs4all.nl>
On Thu, 17 May 2012, Mark Kettenis wrote:
> > So here it is, this change moves *_tdep initialisers to the end while
> > otherwise keeping the order the same (IOW within the two groups the order
> > remains the same as before). I've checked it against autoconf's tool
> > portability list and also verified it with Solaris sed to make sure
> > there are no surprises.
>
> Sorry, but we've always considered it a mistake to rely on a specific
> order of running the initialization functions. Implicit dependencies
> between modules like that really are a bad idea.
What's the technical reason and what do you propose as the alternative?
Personally I see no problems with a hierarchical structure of initialisers
as long as the hierarchy is well-defined so that people can rely on that.
I can give you a name of a complex project that works very well with such
an arrangement, and they actually have as many as eight levels.
Maciej
next prev parent reply other threads:[~2012-05-17 11:23 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 [this message]
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
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=alpine.DEB.1.10.1205171215290.11227@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=thomas@codesourcery.com \
--cc=tromey@redhat.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