comment on

Let me rephrase then. I think any programming language that allows users to define user-named symbols (variables and functions, if not macros, patterns, types, and objects) promotes creating dialects. In fact, I don't think it's possible to solve any interesting problem in a useful way without creating a new dialect!

I consider Spiffy to create a new dialect of Perl 5. I consider IO::All to create a new dialect of Perl 5. I consider CGI to create a new dialect of Perl 5.

Each of those modules adds capabilities that didn't previously exist. If you don't already know how to use them, you'll have to spend time learning them before you can really read and understand code that uses them. Using IO::All means certain things for using bitshift operators in some code. Using CGI in certain cases can do things to STDIN.

Just like most of the new language features in Perl 6, though, if you don't use them you won't pay for them.

In reply to Re^4: Perl 6 critique is a good thing by chromatic
in thread Perl 6 critique is a good thing by Juerd

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks