User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0)
            Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
References: <539432A6.7030205@clear.net.nz> <5395A7A3.7040106@residenset.net>  
            <5395AA02.8040704@morningstar2.co.uk>           
            <CANQYN6x3K5LzThY49V2CYuDj0i6O=M1CJgby9YdS4J6ZDY5UTA@mail.gmail.com>           
            <53BF8686.2060201@morningstar2.co.uk>
            <CANQYN6xf4rqATSeaprCrhK01c0ABU+6drtF7TUEhAu1u0Sqwxg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Message-ID:  <53C0131F.2030404@morningstar2.co.uk>
Date:         Fri, 11 Jul 2014 17:38:55 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Juxtaposition in l3fp
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <CANQYN6xf4rqATSeaprCrhK01c0ABU+6drtF7TUEhAu1u0Sqwxg@mail.gmail.com>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 11/07/2014 17:23, Bruno Le Floch wrote:
> On 7/11/14, Joseph Wright <joseph.wright@morningstar2.co.uk> wrote:
>> On 11/07/2014 00:20, Bruno Le Floch wrote:
>>> should change the precedence of juxtaposition-as-multiplication from
>>> what it currently is (the tightest) to being the same as
>>> multiplication.  In other words, juxtaposition would behave exactly
>>> identically to adding an asterisk.
>>
>> To be clear, continue to allow
>>
>>   2x + 1
>>   2pt + 3cm
>>
>> but with
>>
>>   2x^2 + 2 = 2*(x^2) + 2
>>
>> so for your example 25pc^2 requiring braces (0.25pc)^2?
>>
>>> Would that make sense?  Am I missing something crucial (probably... I
>>> didn't realize when allowing juxtaposition what a mess I was
>>> creating)?
>>
>> Seems OK to me (if I've understood correctly).
> 
> Yes you did.  Cf my other email: how should the change happen?
As I said there, with a 'breaking' change (which sometimes simply can't
be avoided) all we can do is warn that there is one. Write the code and
test properly and I'll worry about the release announcement :-)
--
Joseph Wright