<div dir="ltr"><div><div><div>I like the concept, but, if I'm using a constant that goes beyond the millions, I'd add a comment to what the number is in US format, and tag on what exactly it means, or make the variable name itself mean something. Because reading <br><p><tt><span class="gmail-code"><span class="gmail-kw">const</span> maxLongint <span class="gmail-sym">=</span> <span class="gmail-num">$7fffffff</span><span class="gmail-sym">;<br></span></span></tt></p><p><tt><span class="gmail-code"><span class="gmail-sym">or</span></span></tt></p><p><tt><span class="gmail-code"><span class="gmail-sym">const maxLongint = </span></span></tt><font class="gmail-mono">2147483647;</font></p><p><tt><span class="gmail-code"><span class="gmail-sym"></span></span></tt></p></div><div><font class="gmail-mono">is a bit of a pain, I agree.<br><br></font>That said, underscores aren't what I'd use.<br><br>I love the idea of the IDE (ANY IDE, not just Pascal based) doing some
kind of code highlight for large numbers. Something simple, like
underlining every other group of 3 in large numbers, or every other hex
pair, or every 8 binary set.<br><br></div></div>As for the mono-spaced, no, not ridiculous. If memory serves me correct, I believe you're as old-school as I am when it comes to code (My teeth cut on Vic-20), but I've always preferred mono-spaced fonts in my IDE versus variable width, JUST on the primary basis of legibility of the code itself, ignoring the 'gravy' of lining up text within the code. I always terminal/system/consolas, even in Notepad/PSPad. I barely tolerate variable width font in GMail as I can't change the font easily (But you've sparked an idea >:] ). Figuring out if I'm using a capital I versus a lower l versus a | is quite annoying (Capital EYE versus lower ELL versus pipe). Most of the apps I write (for myself) are list based, or require special formatting are typically fixed width as aligning text is much easier, and I don't have to code special considerations for W and 1 width differences. Forget about the form UI, but even lining up variable declarations and definitions, procedure, function declarations within classes, much easier with fixed width.<br><br></div><br><div><div class="gmail_extra"><div class="gmail_quote">On Mon, Nov 21, 2016 at 9:46 AM, Graeme Geldenhuys <span dir="ltr"><<a href="mailto:mailinglists@geldenhuys.co.uk" target="_blank">mailinglists@geldenhuys.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I don't know about you, but I like this idea implemented in Java 7 and<br>
later.<br>
<br>
<a href="http://jasdhir.blogspot.co.uk/2016/11/using-underscores-in-literals.html" rel="noreferrer" target="_blank">http://jasdhir.blogspot.co.uk/<wbr>2016/11/using-underscores-in-<wbr>literals.html</a><br>
<br>
<br>
I always find it hard to read long numeric literals.<br>
<br>
<br>
Alternatively, without needing compiler changes, the IDE's and<br>
programmer editors should become more clever in how they display source<br>
code (think Elastic Tabstops), and automatically display numeric<br>
literals with slight increase in [render] spacing between certain number<br>
groups. Binary literals could be grouped every eight digits, whereas Hex<br>
could be grouped every 4 and Decimals every 3 digits. The age old rule<br>
of programmer source code always being in a mono-spaced font is<br>
ridiculous for this day and age.<br>
<br>
Regards,<br>
Graeme<br>
<br>
______________________________<wbr>_________________<br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.<wbr>org</a><br>
<a href="http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal" rel="noreferrer" target="_blank">http://lists.freepascal.org/<wbr>cgi-bin/mailman/listinfo/fpc-<wbr>pascal</a><br>
</blockquote></div><br></div></div></div>