[m-rev.] for review: Print version information on two lines.

[Michael Richter]

I cannot believe that I'm seeing this much discussion over a bloody version
string.

https://en.wikipedia.org/wiki/Parkinson%27s_Law_of_Triviality

It should be cerulean with mauve trim.  The bike shed, that is.


On 11 March 2014 11:23, Julien Fischer <jfischer at opturion.com> wrote:

>
>
>
> On Tue, Mar 11, 2014 at 1:44 PM, Julien Fischer <jfischer at opturion.com>wrote:
>
>> On Thu, 6 Mar 2014, Paul Bone wrote:
>>
>>  On Tue, Mar 04, 2014 at 07:23:52PM +1100, Peter Wang wrote:
>>>
>>>> On Tue, 4 Mar 2014 14:43:47 +1100, Paul Bone <paul at bone.id.au> wrote:
>>>>
>>>>> If we're going to change the output then perhaps it would be better to
>>>>>> just drop the word "configured"?
>>>>>>
>>>>>> Mercury Compiler, version rotd-2013-10-01, for
>>>>>> x86_64-unknown-linux-gnu
>>>>>>
>>>>>
>>>>> I don't mind, I don't understand the difference.  If my change is
>>>>> unnecessary then this change is also unnecessary.
>>>>>
>>>>
>>>> I didn't say otherwise.  I mooted an alternative way to satisfy your
>>>> goal.  It's closer to the old format and IMO it looks better, so I find
>>>> it easier to scan visually.  I thought it's worth consideration.
>>>>
>>>>
>>> Okay,
>>>
>>> I think this is reasonable, and I'm not sure which 'looks better' so if
>>> you
>>> think this looks better I'm happy to go with that.  I also want to change
>>> the word "for" to "on"
>>>
>>>    Mercury Compiler, version rotd-2013-10-01, on x86_64-unknown-linux-gnu
>>>
>>
>> I disagree with changing "for" to "on".  There are two possible
>> architectures you might report here: the host architecture (i.e.  what
>> mmc is running on) and the target architecture (i.e. what mmc is
>> generating code for).  The architecture string reported in the version
>> message is the latter, and "for" seems the more appropriate preposition.
>> For example if I have a mingw cross-compiler on Linux, mmc will (with
>> your change) now report:
>>
>
> Actually, ignore that it's not the target architecture it's reporting
> after all, it's
> whatever MR_FULLARCH was set to in the library that mmc was linked against.
> I think that since we now support cross compiling it would be more
> sensible to
> do something like:
>
>    Mercury Compiler, version 14.01
>    Copyright (C) ... etc etc
>    Host: x86_64-unknown-linux-gnu
>    Target: i686-pc-mingw32
>    Usage: mmc [<options>] <arguments>
>    Use `mmc --help' for more information.
>
> where Target is the architecture string from the Mercury.config file (if
> available).
>
> Cheers,
> Julien.
>
>
>
>
>
>
> _______________________________________________
> reviews mailing list
> reviews at lists.mercurylang.org
> https://www.mercurylang.org/lists/listinfo/reviews
>
>


-- 
"Perhaps people don't believe this, but throughout all of the discussions
of entering China our focus has really been what's best for the Chinese
people. It's not been about our revenue or profit or whatnot."
--Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20140311/d040302f/attachment.html>