1: Auto-semicolons are bad. Look at Javascript. Who deliberately uses them? Nobody. Who occasionally needs to workaround them? Everybody.

2: Runaway quotes are usually caught anyway; it's just the error message happens several lines further than you expect it to be. For a missing quote mark not to cause a syntax error requires a perfect storm of conditions. (Usually involving quote marks being used in comments.) To anybody using editors with syntax highlighting, this isn't usually much of an issue anyway. I don't think it's necessarily a bad idea, as long as heredocs are exempt. I just don't think it gives us much.

3a: I see no use for this feature. What would it be used for?

3b: It's already possible to close multiple levels of braces on one line. The syntax for it is: }}. You even have fine-grained control over how many levels you close. If you want to close four levels, use }}}}. If you're closing less than four levels, this existing syntax is as compact or more compact than what you suggest. If you're routinely closing more than four levels, consider restructuring your code so it doesn't have so many deeply nested blocks.

4a: The frequently used built-ins mostly have pretty short names anyway. Any shorter and they lose descriptiveness. I don't see how this is a win.

4b: I don't know exactly what you mean.

4c: I really need to fix up my macros implementation and put it on CPAN.

5a: I guess this is a decent one.

5b: By translation table, you mean tr///? Seems like overkill.

5c/5d: head, tail, trim, ltrim, and rtrim are so trivial to implement, I don't see the need for them to be in core. There's a bunch of implementations on CPAN already.

6: for what purpose?

7: global variables are design smell. "Let's introduce new features for global variables" is like saying "let's make the two-argument open more powerful".

8a: It's not hard to check if the return value of index is below a certain limit.

8b: Don't the existing substr and splice functions do this?

9a: Umm, when is already allowed in for loops.

9b: I don't understand what's made easier by this.


In reply to Re: What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff by tobyink
in thread What esteemed monks think about changes necessary/desirable in Perl 7 outside of OO staff by likbez

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.