GNU logs - #16638, boring messages

Message sent to bug-libtool@HIDDEN:

Subject: bug#16638: I was hoping the Libtool would manage ordering for me
Resent-From: Dave Yost <Dave@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Tue, 04 Feb 2014 07:25:01 +0000
Resent-Message-ID: <handler.16638.B.13914986446474 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 16638 <at> debbugs.gnu.org
From: Dave Yost <Dave@HIDDEN>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-Id: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
Date: Mon, 3 Feb 2014 23:23:34 -0800
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1870\))
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Our code base loads .o files in a specified order so that initialization =
code is called in the desired order.

While looking for this feature in Libtool, I noted that the =
documentation uses =93in order to=94 many times. Those usages can be =
streamlined by removing =93in order=94 and just going with =93to=94.

If you are interested in putting an ordering feature into Libtool, I bet =
we could give you our code.

Thanks=

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Dave Yost <Dave@HIDDEN>
Subject: bug#16638: Acknowledgement (I was hoping the Libtool would manage
 ordering for me)
Message-ID: <handler.16638.B.13914986446474.ack <at> debbugs.gnu.org>
References: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
X-Gnu-PR-Message: ack 16638
X-Gnu-PR-Package: libtool
Reply-To: 16638 <at> debbugs.gnu.org
Date: Tue, 04 Feb 2014 07:25:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-libtool@HIDDEN

If you wish to submit further information on this problem, please
send it to 16638 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
16638: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D16638
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-libtool@HIDDEN:

Subject: bug#16638: BTW
References: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
In-Reply-To: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
Resent-From: Dave Yost <Dave@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Tue, 04 Feb 2014 09:12:01 +0000
Resent-Message-ID: <handler.16638.B16638.139150510516318 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 16638 <at> debbugs.gnu.org
From: Dave Yost <Dave@HIDDEN>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D251FAC-88E1-4007-A517-620A18EFECCF@HIDDEN>
Date: Tue, 4 Feb 2014 01:11:39 -0800
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1870\))
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Whoever wrote this documentation is my hero. It=92s wonderful. Very =
clear and also fun.=

Message sent to bug-libtool@HIDDEN:

Subject: bug#16638: I was hoping the Libtool would manage ordering for me
Resent-From: "Gary V. Vaughan" <gary@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Wed, 05 Feb 2014 06:07:02 +0000
Resent-Message-ID: <handler.16638.B16638.139158039832041 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Dave Yost <Dave@HIDDEN>
Cc: "16638 <at> debbugs.gnu.org" <16638 <at> debbugs.gnu.org>
References: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
Mime-Version: 1.0 (1.0)
In-Reply-To: <16B4E921-F3CF-46AB-A824-F673A6052C4C@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AB7F92F-76DE-4BE7-A12D-7B2D83610BB8@HIDDEN>
From: "Gary V. Vaughan" <gary@HIDDEN>
Date: Wed, 5 Feb 2014 19:06:30 +1300
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Dave,

On Feb 4, 2014, at 8:23 PM, Dave Yost <Dave@HIDDEN> wrote:
> Our code base loads .o files in a specified order so that initialization c=
ode is called in the desired order.

That's not something I've encountered before. So it must be a C++ thing?

> While looking for this feature in Libtool, I noted that the documentation u=
ses =E2=80=9Cin order to=E2=80=9D many times. Those usages can be streamline=
d by removing =E2=80=9Cin order=E2=80=9D and just going with =E2=80=9Cto=E2=80=
=9D.

That's a weird tick I've developed, thanks for pointing it out. Without the b=
enefit of an editor, it's easy to let unnecessary verbiage like that sneak i=
n. Thanks for the reminder, I'll go through and cut where I can.

> If you are interested in putting an ordering feature into Libtool, I bet w=
e could give you our code.

Patches welcome, as always!

Note that the the FSF requires copyright assignments on file before I can pu=
sh any non-trivial changes. Please contact me off-list if you'd like to get t=
he process started - it takes a few weeks, so is worth doing in case you wan=
t to send any patches in future, even if this "in order object files" propos=
al doesn't go through for some reason.

Cheers,
--=20
Gary V. Vaughan (gary AT vaughan DOT pe)

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.