Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Perl 5.16 and beyond
Jesse Vincent
jesse@perl.org
@obra
Perl 6




   Recovering Perl 6
   Project Manager
Perl 6




   Recovering Perl 6
   Project Manager
Perl 5




Perl 5 Pumpking
Perl 5




Perl 5 Pumpking
Perl 5




Perl 5 Pumpking
Perl 5




Perl 5 Pumpking



          http://flic.kr/p/6StRmB
Perl 5




Perl 5 Pumpking
?




What's a Pumpking?
BDFL
BDFL
BDFL
I make decisions
(          )




(the unpopular ones)
I delegate
(                     )




    (any real work)
I document
(            )




(process and policy)
I destress
(      )




(other people)
I’m a manager
Perl         ?




So, who makes Perl?
Many awesome people
I just stand
around
looking
pretty...
...while other people do
     awesome stuff
Perl AUTHORS               ?




  Is your name in Perl’s
    AUTHORS file?
CPAN   ?




  Are you a
CPAN author?
You rock
Perl




You make Perl
Perl




The rules of
Perl Club
commit e8cd7eae0498ecc1fd3801fe3160
Author: Gurusamy Sarathy <gsar@cpan.org>
Date:   Sun Oct 10 23:48:07 1999 +0000

add p...
1




Rule 1
Perl



  Larry is always
 right about how
Perl should behave
2




Rule 2
Larry is allowed to
 change his mind
about any matter
 at a later date...
...regardless
   of whether
 he previously
invoked Rule 1
I’m not Larry
I’m nowhere
 near as clever
My shirts are
nowhere near
  as loud
My shirts are
nowhere near
  as loud
The rules aren’t
just for Larry
The rules aren’t
just for the Pumpking
Perl 5




  The rules also apply
   to the Perl 5 core.
?




What?
1




Rule 1
Perl




Perl is always right!
(                )




    (TMTOWTDI)
2




Rule 2
Perl 5




The Perl 5 core
is allowed to...
?




change its mind?
Changing our
minds is easy
We are very
 good at it
Not flailing wildly when
we do has been hard
...and leads to
  problems
at least I haven’t
  heard this
   in a while...
Perl




Perl is Dead !
Perl




Perl is Dead !1!!
Perl




Perl is Dead !1!!one!
What I’ve been
hearing lately...
?




Where are we going?
It’s changing too fast.
Can you slow down?
?


 You made regexes
crazier? /$#@!/l?
smartmatch isn’t
named correctly...
we should call it
 psychoticmatch
?



Now that it’s undead,
can we rename it?
I’ve been accused
     of lacking a
vision for Perl 5
What
I lack



is a flame-proof suit
             http://en.wikipedia.org/wiki/File:Dance_Dance_Immolation.jpg
pe
What       rl5
I lack         -po
                     rt
                        e       rs



is a flame-proof suit
  ...
2




 If I’d talked about my
vision 2 years ago...
You would have
laughed at me
Perl 5




  Improving Perl 5
 did not matter
We couldn’t even
put out a new release
In the past year...
5



 Five
 Stable
Releases
1



 A dozen
development
  releases
Perl 5.14.2



Perl 5.14.2 is the
current stable
release of Perl 5
9




It came out in
September
3



  It used to take us
3 weeks to prepare
       a release
We made the
Pumpking do it
1




  Now it takes
less than a day
43




 The 43 step process is
    documented
We have rotating
release engineers
Many of them are
new committers
Release engineers
need commit bits
git



 Since the switch to git,
 we’ve nearly doubled
   our committer list
The world
hasn’t ended
Some of those release
engineers have become
 prolific contributors
Now that
releases
are easy...
Perl 5




A Vision for Perl 5
New versions of Perl 5
should not break
your existing software
Old syntax and
     semantics
 must not stop
Perl 5 from evolving
Perl 5



We need to be able to
 make mistakes
 as we rebuild Perl 5
We will
   make mistakes
as we rebuild Perl 5
We have
  made mistakes
as we’ve rebuilt Perl 5
We need to be able to
recover from mistakes
  as we rebuild Perl 5
The runtime is
too big and must be
   slimmed down
Perl should have
sane defaults
We need to be able to
 recover from last
year’s “sane defaults”
Perl 5   Perl 5



It should be possible
   to build more of
  Perl 5 in Perl 5
Perl should run
everywhere
2: Perl



      Rule 2:
Perl is allowed to
 change its mind
That’s already true
That hurts programs
  and programmers
When your code runs,
 you have no idea
what semantics it’ll see
use v5.14;
5.14   Perl      ?




“Can I have a Perl that’s
  5.14 or newer?”
5.14.0                  !



 “Anything newer than
   5.14.0 would be
       great!”
OK    5.30            !




     “Ok. I’m 5.30.
       Have fun!”
That is not useful
It needs to change
Perl 5



From now on, declare
  the version of Perl 5
      you expect
use v5.16;
5.16        Perl 5




  “I want a Perl 5 that
  works like 5.16”
The runtime should
honor that request
Perl should give you
semantics as close as
possible to what you
         request
New features
should not work
under ‘use v5.$older;’
It’s critical that we be
     able to evolve
We need an
escape hatch
We need
Rule 2
If you declare an old
 version, you get old
  syntax and semantics
...at least to the
best of our abilities
Perfection is
not possible
We can get far closer
  than we do now
Breaking existing
 code should be
 a last resort
In limited
circumstances we will
    break backward
     compatibility
Some craziness can’t be
fixed in an “optional”
    or lexical way
This is going to be
  hard work
A lot of hard work
It’s not impossible
Deprecation
1



  Our current
deprecation cycle
   is 1 year
5.16.0




 “It warns in 5.16.0”
5.18.0




“It’s gone in 5.18.0”
That’s turning out
to be too short
OS


Very few operating
systems release that
     frequently
Declare by default
 means we can make
some changes sooner
If it still works in
 old code, we get to
  change it with no
deprecation cycle
Some misfeatures
need to come out
lest they block major
    improvements
If we can’t emulate
 an old feature for old
code, we get a longer
 deprecation cycle
'use v5.16'      die




 “It dies in code that
declares ‘use v5.16’”
5.16.0




         “It warns in older
           code on 5.16.0”
5.18.0




    “It still warns in old
       code on 5.18.0”
5.20.0




“It’s gone in 5.20.0”
2




 Rule 2 and
Old Modules
We haven’t just been
deprecating and yanking
 broken old features
We’ve been doing the
same to old modules
CPAN




They all end up
  on CPAN
This hurts users who
   wrote code with
“no non-core deps”
2    Perl 5



We need to make it
easier to ship two
 flavors of Perl 5
(Eagles)




Hotel California
Last thing I remember, I was
Running for the door
I had to find the passage back
To the place I was before
’relax,’ said t...
Perl




aka Traditional Perl
(Bob Dylan)




The Times,They
Are A-Changin’
The line it is drawn
The curse it is cast
The slow one now
Will later be fast
As the present now
Will later be past
The or...
Perl




aka Bootstrappable Perl
There’s work going on
  to make this easier
Perl




Perl is a big language
There are bigger
    languages
It's harder to manage
      a big language
It’s harder to learn
     a big language
It’s harder to fix bugs in
       a big language
We’re ok, but not
amazing at core
language dev
Perl




  As a community, we’re
  awesome at modules
Perl
                ?


How do we make Perl
a smaller language?
It’s possible to load
modules that inject
     new builtins
It’s possible to load
modules that inject
     old builtins
Time to start...
...refactoring
Lots of stuff in perl isn't
  necessarily part of
 Perl 5 the language
Perl 5




    This stuff is part of
   Perl 5 the chainsaw
I like our chainsaw
I’m not talking about
 deprecating this stuff
...just about
decoupling it
SysV   IPC




SysV IPC functions
Socket IO




Socket IO functions
Unix    /




   Unix user & group
 information functions
Unix




    Unix network
information functions
Process and process
  group functions
Formats
smartmatch
...and probably a bunch
      of other stuff
'use v5.16'
 5.14


If you don’t ‘use v5.16’,
you’ll get whatever was
         in 5.14.
SysV



  The implementation of
     SysV might be a
        module
As a Perl 5 user you
 won’t need to care
..and shouldn’t
 be able to tell
In the future we might
fix a bug or two in the
   modularized code
Perl 5


  You could take the
    update without
 having to upgrade all of
          Perl 5
Someday we might
remove things from the
   default runtime
Every feature we
externalize reclaims
precious memory
Every feature we
externalize reclaims
 precious sanity
That just means you’ll
 need to declare you
want an older feature
v5.16




...but only if you
   ask for v5.16
v5.18




...but only if you
   ask for v5.18
v5.20




...but only if you
   ask for v5.20
Existing code
won’t break
There are many, many
   unanswered
     questions
But it’s doable
Perl




   We've been moving
       pretty fast
We’ve done some
   things I...
would not
do again
I’m going to be a lot
more skeptical about
   new features
...at least ones that
don’t make it easier to
 have fewer features
We should have
sane defaults
Perl 5




  There’s lots of crazy
        in Perl 5
Syntactic Crazy
Semantic Crazy
Internal Crazy
Module Crazy
It may be time to
consider doing away
  with some of that
We’ve started
down this road
"use v5.12"   "use strict;"



        “use v5.12”
          includes
       “use strict;”
?




Where do we
 go next?
warnings




warnings on
 by default
autodie




autodie-esque
   defaults
return


 We should throw
exceptions rather
 than just return on
        failure
I don’t want us to
   bikeshed an
exception hierarchy
Heck, I’d be happy if we
started with dying with
 well-defined strings
(                                       )




    (I’d love an exception hierarchy)
2    open()




    2-arg open()
    gone by default
1    open()




    1-arg open()
    gone by default
No more ' package
   separator
Latin-1



             Latin-1
          autopromote
           off by default
utf-8




utf-8 everything
     by default
A clean, simple
meta-model
 with classes
and methods
No indirect object
 syntax by default
"use v5.16"




But only if you declare
     “use v5.16”
"use v5.18"




But only if you declare
     “use v5.18”
"use v5.20"




But only if you declare
     “use v5.20”
Perl



    Perl needs to be
  cleaner, simpler
     and easier
     to work with
For users...
...and for
implementers
Perl




       Perl should run
       everywhere
Not just on every
kind of hardware
OS




 Not just on every
Operating System
VM




Every VM
Every Browser
Every Phone
Perl 5       ?


Why isn’t Perl 5 on
other runtimes?
“There’s no spec”
Ruby




That didn’t stop Ruby
Perl 5       Perl 5




  “Only Perl 5 can
    parse Perl 5”
PPI




That didn't stop PPI
Perl 5



 To survive, a desperate
 hacker needs to be able
to reimplement Perl 5
Thanks!
Super-thanks
individual
 sponsors!
Questions?
http://blog.fsck.com
jesse@perl.org
@obra
?



So, you want
 to change
the name?
Perl 7   ?




To something like
    Perl 7?
Or Raptor?
Perl 5



Our language
  is called
   Perl 5
Perl 6



  Perl 6 is our
   precocious
    kid sister
Perl 5




I’m happy to talk about
  renaming Perl 5...
...if you write me a
second implementation
...that passes the
     test suite
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
So, I made a keyboard
Next
Upcoming SlideShare
So, I made a keyboard
Next
Download to read offline and view in fullscreen.

1

Share

Perl 5.16 and Beyond - YAPC::Asia 2011

Download to read offline

Related Books

Free with a 30 day trial from Scribd

See all

Perl 5.16 and Beyond - YAPC::Asia 2011

  1. 1. Perl 5.16 and beyond Jesse Vincent jesse@perl.org @obra
  2. 2. Perl 6 Recovering Perl 6 Project Manager
  3. 3. Perl 6 Recovering Perl 6 Project Manager
  4. 4. Perl 5 Perl 5 Pumpking
  5. 5. Perl 5 Perl 5 Pumpking
  6. 6. Perl 5 Perl 5 Pumpking
  7. 7. Perl 5 Perl 5 Pumpking http://flic.kr/p/6StRmB
  8. 8. Perl 5 Perl 5 Pumpking
  9. 9. ? What's a Pumpking?
  10. 10. BDFL
  11. 11. BDFL
  12. 12. BDFL
  13. 13. I make decisions
  14. 14. ( ) (the unpopular ones)
  15. 15. I delegate
  16. 16. ( ) (any real work)
  17. 17. I document
  18. 18. ( ) (process and policy)
  19. 19. I destress
  20. 20. ( ) (other people)
  21. 21. I’m a manager
  22. 22. Perl ? So, who makes Perl?
  23. 23. Many awesome people
  24. 24. I just stand around looking pretty...
  25. 25. ...while other people do awesome stuff
  26. 26. Perl AUTHORS ? Is your name in Perl’s AUTHORS file?
  27. 27. CPAN ? Are you a CPAN author?
  28. 28. You rock
  29. 29. Perl You make Perl
  30. 30. Perl The rules of Perl Club
  31. 31. commit e8cd7eae0498ecc1fd3801fe3160 Author: Gurusamy Sarathy <gsar@cpan.org> Date: Sun Oct 10 23:48:07 1999 +0000 add perlhack.pod from Nathan Torkington <gnat@frii.com>
  32. 32. 1 Rule 1
  33. 33. Perl Larry is always right about how Perl should behave
  34. 34. 2 Rule 2
  35. 35. Larry is allowed to change his mind about any matter at a later date...
  36. 36. ...regardless of whether he previously invoked Rule 1
  37. 37. I’m not Larry
  38. 38. I’m nowhere near as clever
  39. 39. My shirts are nowhere near as loud
  40. 40. My shirts are nowhere near as loud
  41. 41. The rules aren’t just for Larry
  42. 42. The rules aren’t just for the Pumpking
  43. 43. Perl 5 The rules also apply to the Perl 5 core.
  44. 44. ? What?
  45. 45. 1 Rule 1
  46. 46. Perl Perl is always right!
  47. 47. ( ) (TMTOWTDI)
  48. 48. 2 Rule 2
  49. 49. Perl 5 The Perl 5 core is allowed to...
  50. 50. ? change its mind?
  51. 51. Changing our minds is easy
  52. 52. We are very good at it
  53. 53. Not flailing wildly when we do has been hard
  54. 54. ...and leads to problems
  55. 55. at least I haven’t heard this in a while...
  56. 56. Perl Perl is Dead !
  57. 57. Perl Perl is Dead !1!!
  58. 58. Perl Perl is Dead !1!!one!
  59. 59. What I’ve been hearing lately...
  60. 60. ? Where are we going?
  61. 61. It’s changing too fast. Can you slow down?
  62. 62. ? You made regexes crazier? /$#@!/l?
  63. 63. smartmatch isn’t named correctly...
  64. 64. we should call it psychoticmatch
  65. 65. ? Now that it’s undead, can we rename it?
  66. 66. I’ve been accused of lacking a vision for Perl 5
  67. 67. What I lack is a flame-proof suit http://en.wikipedia.org/wiki/File:Dance_Dance_Immolation.jpg
  68. 68. pe What rl5 I lack -po rt e rs is a flame-proof suit http://en.wikipedia.org/wiki/File:Dance_Dance_Immolation.jpg
  69. 69. 2 If I’d talked about my vision 2 years ago...
  70. 70. You would have laughed at me
  71. 71. Perl 5 Improving Perl 5 did not matter
  72. 72. We couldn’t even put out a new release
  73. 73. In the past year...
  74. 74. 5 Five Stable Releases
  75. 75. 1 A dozen development releases
  76. 76. Perl 5.14.2 Perl 5.14.2 is the current stable release of Perl 5
  77. 77. 9 It came out in September
  78. 78. 3 It used to take us 3 weeks to prepare a release
  79. 79. We made the Pumpking do it
  80. 80. 1 Now it takes less than a day
  81. 81. 43 The 43 step process is documented
  82. 82. We have rotating release engineers
  83. 83. Many of them are new committers
  84. 84. Release engineers need commit bits
  85. 85. git Since the switch to git, we’ve nearly doubled our committer list
  86. 86. The world hasn’t ended
  87. 87. Some of those release engineers have become prolific contributors
  88. 88. Now that releases are easy...
  89. 89. Perl 5 A Vision for Perl 5
  90. 90. New versions of Perl 5 should not break your existing software
  91. 91. Old syntax and semantics must not stop Perl 5 from evolving
  92. 92. Perl 5 We need to be able to make mistakes as we rebuild Perl 5
  93. 93. We will make mistakes as we rebuild Perl 5
  94. 94. We have made mistakes as we’ve rebuilt Perl 5
  95. 95. We need to be able to recover from mistakes as we rebuild Perl 5
  96. 96. The runtime is too big and must be slimmed down
  97. 97. Perl should have sane defaults
  98. 98. We need to be able to recover from last year’s “sane defaults”
  99. 99. Perl 5 Perl 5 It should be possible to build more of Perl 5 in Perl 5
  100. 100. Perl should run everywhere
  101. 101. 2: Perl Rule 2: Perl is allowed to change its mind
  102. 102. That’s already true
  103. 103. That hurts programs and programmers
  104. 104. When your code runs, you have no idea what semantics it’ll see
  105. 105. use v5.14;
  106. 106. 5.14 Perl ? “Can I have a Perl that’s 5.14 or newer?”
  107. 107. 5.14.0 ! “Anything newer than 5.14.0 would be great!”
  108. 108. OK 5.30 ! “Ok. I’m 5.30. Have fun!”
  109. 109. That is not useful
  110. 110. It needs to change
  111. 111. Perl 5 From now on, declare the version of Perl 5 you expect
  112. 112. use v5.16;
  113. 113. 5.16 Perl 5 “I want a Perl 5 that works like 5.16”
  114. 114. The runtime should honor that request
  115. 115. Perl should give you semantics as close as possible to what you request
  116. 116. New features should not work under ‘use v5.$older;’
  117. 117. It’s critical that we be able to evolve
  118. 118. We need an escape hatch
  119. 119. We need Rule 2
  120. 120. If you declare an old version, you get old syntax and semantics
  121. 121. ...at least to the best of our abilities
  122. 122. Perfection is not possible
  123. 123. We can get far closer than we do now
  124. 124. Breaking existing code should be a last resort
  125. 125. In limited circumstances we will break backward compatibility
  126. 126. Some craziness can’t be fixed in an “optional” or lexical way
  127. 127. This is going to be hard work
  128. 128. A lot of hard work
  129. 129. It’s not impossible
  130. 130. Deprecation
  131. 131. 1 Our current deprecation cycle is 1 year
  132. 132. 5.16.0 “It warns in 5.16.0”
  133. 133. 5.18.0 “It’s gone in 5.18.0”
  134. 134. That’s turning out to be too short
  135. 135. OS Very few operating systems release that frequently
  136. 136. Declare by default means we can make some changes sooner
  137. 137. If it still works in old code, we get to change it with no deprecation cycle
  138. 138. Some misfeatures need to come out lest they block major improvements
  139. 139. If we can’t emulate an old feature for old code, we get a longer deprecation cycle
  140. 140. 'use v5.16' die “It dies in code that declares ‘use v5.16’”
  141. 141. 5.16.0 “It warns in older code on 5.16.0”
  142. 142. 5.18.0 “It still warns in old code on 5.18.0”
  143. 143. 5.20.0 “It’s gone in 5.20.0”
  144. 144. 2 Rule 2 and Old Modules
  145. 145. We haven’t just been deprecating and yanking broken old features
  146. 146. We’ve been doing the same to old modules
  147. 147. CPAN They all end up on CPAN
  148. 148. This hurts users who wrote code with “no non-core deps”
  149. 149. 2 Perl 5 We need to make it easier to ship two flavors of Perl 5
  150. 150. (Eagles) Hotel California
  151. 151. Last thing I remember, I was Running for the door I had to find the passage back To the place I was before ’relax,’ said the night man, We are programmed to receive. You can checkout any time you like, But you can never leave!
  152. 152. Perl aka Traditional Perl
  153. 153. (Bob Dylan) The Times,They Are A-Changin’
  154. 154. The line it is drawn The curse it is cast The slow one now Will later be fast As the present now Will later be past The order is rapidly fadin’ And the first one now will later be last For the times they are a-changin’
  155. 155. Perl aka Bootstrappable Perl
  156. 156. There’s work going on to make this easier
  157. 157. Perl Perl is a big language
  158. 158. There are bigger languages
  159. 159. It's harder to manage a big language
  160. 160. It’s harder to learn a big language
  161. 161. It’s harder to fix bugs in a big language
  162. 162. We’re ok, but not amazing at core language dev
  163. 163. Perl As a community, we’re awesome at modules
  164. 164. Perl ? How do we make Perl a smaller language?
  165. 165. It’s possible to load modules that inject new builtins
  166. 166. It’s possible to load modules that inject old builtins
  167. 167. Time to start...
  168. 168. ...refactoring
  169. 169. Lots of stuff in perl isn't necessarily part of Perl 5 the language
  170. 170. Perl 5 This stuff is part of Perl 5 the chainsaw
  171. 171. I like our chainsaw
  172. 172. I’m not talking about deprecating this stuff
  173. 173. ...just about decoupling it
  174. 174. SysV IPC SysV IPC functions
  175. 175. Socket IO Socket IO functions
  176. 176. Unix / Unix user & group information functions
  177. 177. Unix Unix network information functions
  178. 178. Process and process group functions
  179. 179. Formats
  180. 180. smartmatch
  181. 181. ...and probably a bunch of other stuff
  182. 182. 'use v5.16' 5.14 If you don’t ‘use v5.16’, you’ll get whatever was in 5.14.
  183. 183. SysV The implementation of SysV might be a module
  184. 184. As a Perl 5 user you won’t need to care
  185. 185. ..and shouldn’t be able to tell
  186. 186. In the future we might fix a bug or two in the modularized code
  187. 187. Perl 5 You could take the update without having to upgrade all of Perl 5
  188. 188. Someday we might remove things from the default runtime
  189. 189. Every feature we externalize reclaims precious memory
  190. 190. Every feature we externalize reclaims precious sanity
  191. 191. That just means you’ll need to declare you want an older feature
  192. 192. v5.16 ...but only if you ask for v5.16
  193. 193. v5.18 ...but only if you ask for v5.18
  194. 194. v5.20 ...but only if you ask for v5.20
  195. 195. Existing code won’t break
  196. 196. There are many, many unanswered questions
  197. 197. But it’s doable
  198. 198. Perl We've been moving pretty fast
  199. 199. We’ve done some things I...
  200. 200. would not do again
  201. 201. I’m going to be a lot more skeptical about new features
  202. 202. ...at least ones that don’t make it easier to have fewer features
  203. 203. We should have sane defaults
  204. 204. Perl 5 There’s lots of crazy in Perl 5
  205. 205. Syntactic Crazy
  206. 206. Semantic Crazy
  207. 207. Internal Crazy
  208. 208. Module Crazy
  209. 209. It may be time to consider doing away with some of that
  210. 210. We’ve started down this road
  211. 211. "use v5.12" "use strict;" “use v5.12” includes “use strict;”
  212. 212. ? Where do we go next?
  213. 213. warnings warnings on by default
  214. 214. autodie autodie-esque defaults
  215. 215. return We should throw exceptions rather than just return on failure
  216. 216. I don’t want us to bikeshed an exception hierarchy
  217. 217. Heck, I’d be happy if we started with dying with well-defined strings
  218. 218. ( ) (I’d love an exception hierarchy)
  219. 219. 2 open() 2-arg open() gone by default
  220. 220. 1 open() 1-arg open() gone by default
  221. 221. No more ' package separator
  222. 222. Latin-1 Latin-1 autopromote off by default
  223. 223. utf-8 utf-8 everything by default
  224. 224. A clean, simple meta-model with classes and methods
  225. 225. No indirect object syntax by default
  226. 226. "use v5.16" But only if you declare “use v5.16”
  227. 227. "use v5.18" But only if you declare “use v5.18”
  228. 228. "use v5.20" But only if you declare “use v5.20”
  229. 229. Perl Perl needs to be cleaner, simpler and easier to work with
  230. 230. For users...
  231. 231. ...and for implementers
  232. 232. Perl Perl should run everywhere
  233. 233. Not just on every kind of hardware
  234. 234. OS Not just on every Operating System
  235. 235. VM Every VM
  236. 236. Every Browser
  237. 237. Every Phone
  238. 238. Perl 5 ? Why isn’t Perl 5 on other runtimes?
  239. 239. “There’s no spec”
  240. 240. Ruby That didn’t stop Ruby
  241. 241. Perl 5 Perl 5 “Only Perl 5 can parse Perl 5”
  242. 242. PPI That didn't stop PPI
  243. 243. Perl 5 To survive, a desperate hacker needs to be able to reimplement Perl 5
  244. 244. Thanks!
  245. 245. Super-thanks individual sponsors!
  246. 246. Questions? http://blog.fsck.com jesse@perl.org @obra
  247. 247. ? So, you want to change the name?
  248. 248. Perl 7 ? To something like Perl 7?
  249. 249. Or Raptor?
  250. 250. Perl 5 Our language is called Perl 5
  251. 251. Perl 6 Perl 6 is our precocious kid sister
  252. 252. Perl 5 I’m happy to talk about renaming Perl 5...
  253. 253. ...if you write me a second implementation
  254. 254. ...that passes the test suite
  • sharifulin

    Oct. 19, 2011

Views

Total views

2,789

On Slideshare

0

From embeds

0

Number of embeds

441

Actions

Downloads

19

Shares

0

Comments

0

Likes

1

×