[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Probably bug in implementation of numerical constant parsing
- From: "M. Edward (Ed) Borasky" <znmeb@...>
- Date: Tue, 18 Sep 2012 12:29:30 -0700
On Tue, Sep 18, 2012 at 12:19 PM, Rena <email@example.com> wrote:
> On 2012-09-18 9:00 AM, "Philippe Lhoste" <PhiLho@gmx.net> wrote:
>> On 17/09/2012 18:08, Egor Skriptunoff wrote:
>>> On 9/17/12, Miles Bader <firstname.lastname@example.org> wrote:
>>>> Luiz Henrique de Figueiredo <email@example.com> writes:
>>>>> The same problem occurs with
>>>> But, why would anybody write that instead of print("64"..s) ?
>>> I stumbled upon it when I was trying to write something like this:
>>> print(n+1..' rabbits')
>> Sometime, I dream of a language forcing to put whitespace around
>> I believe it helps readability, and it would reduce or eliminate such
>> But I don't know if it would be popular, some programmers like compact
>> code (or hate typing, but a good IDE can help here).
>> Philippe Lhoste
>> -- (near) Paris -- France
>> -- http://Phi.Lho.free.fr
>> -- -- -- -- -- -- -- -- -- -- -- -- -- --
> That might be nice until I have to break an 82-character line in two instead
> of just removing the spaces in 'x + 1'... I find having to split something
> into multiple lines harms readability quite a bit at times, so I sometimes
> remove spaces to make it fit.
Since most languages I read / write regularly have the "open syntactic
element means the next line is a continuation of this one" feature, I
tend to break lines *for* readability. At least Perl, R, Ruby and Lua
operate this way.
Twitter: http://twitter.com/znmeb; Computational Journalism Publishers
How the Hell can the lion sleep with all those people singing "A weem
oh way!" at the top of their lungs?