comment on

As seen on #perl6:

apr 19 01:22:02 <polettix>
         <disclaimer>I'm not asking for dates!</disclaimer> what perce
+ntage of
         Perl 6 specs definition do you think we (well... you) are at?
apr 19 01:22:56 <TimToady>
         we're well past the first 80% and well into the second 80%.  
+:)
apr 19 01:23:52 <polettix>
         nice answer, and I suspect it also represents the reality qui
+te well :)
apr 19 01:23:56 <TimToady>
         in other words, most of the important stuff is done, and much
+ of what
         remains is a protracted negotiation between the current desig
+n and the
         implementors
apr 19 01:24:26 <TimToady>
         with assorted input from educators and users
apr 19 01:25:29 <TimToady>
         plus a gentle undercurrent of "keep everything else the same 
+as Perl 5"
[download]

I hope I'm not being rude "publishing" these log lines without explicit permission (but I already did in the past:)

Flavio
perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Don't fool yourself.

In reply to Re: How much Perl6 have we got? (take 2) by polettix
in thread How much Perl6 have we got? (take 2) by bronto

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.


P is for Practical
	PerlMonks