| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
|---|
| 2 | <html lang="en"> |
|---|
| 3 | <head> |
|---|
| 4 | <link href="perl.css" rel="stylesheet" type="text/css"> |
|---|
| 5 | <meta content="text/html; charset=UTF-8" http-equiv="content-type"> |
|---|
| 6 | <title>Pugs Apocryphon 1</title> |
|---|
| 7 | <meta content="Audrey Tang" name="author"> |
|---|
| 8 | </head> |
|---|
| 9 | <body> |
|---|
| 10 | <h1 style="text-align: left; line-height: normal;" align="left"> |
|---|
| 11 | Pugs |
|---|
| 12 | Apocryphon 1<br> |
|---|
| 13 | <span style="font-weight: normal;">Overview |
|---|
| 14 | of the Pugs project</span></h1> |
|---|
| 15 | <h2> |
|---|
| 16 | What is this document about?</h2> |
|---|
| 17 | <p> |
|---|
| 18 | The <a href="http://svn.perl.org/perl6/pugs/trunk/docs/">Pugs |
|---|
| 19 | Apocrypha</a> |
|---|
| 20 | are a series of documents, written in question/answer format, to |
|---|
| 21 | explain the |
|---|
| 22 | design and implementation of Pugs. This document (PA01) is a |
|---|
| 23 | higher-level |
|---|
| 24 | overview of the project.</p> |
|---|
| 25 | <h2> |
|---|
| 26 | What is Pugs?</h2> |
|---|
| 27 | <p> |
|---|
| 28 | Started in February 2005, <a href="http://pugscode.org/">Pugs</a> |
|---|
| 29 | is an implementation of the Perl 6 |
|---|
| 30 | language. <a href="http://use.perl.org/%7Eautrijus/journal/">Autrijus |
|---|
| 31 | Tang</a> is responsible for the |
|---|
| 32 | design and development of Pugs with help from a group of committers and |
|---|
| 33 | contributors.</p> |
|---|
| 34 | <h2> |
|---|
| 35 | What is Perl 6?</h2> |
|---|
| 36 | <p> |
|---|
| 37 | <a href="http://dev.perl.org/perl6/">Perl |
|---|
| 38 | 6</a> |
|---|
| 39 | is the next major revision of Perl, a context-sensitive, |
|---|
| 40 | multi-paradigmatic, <i>practical</i> |
|---|
| 41 | programming language, designed by a team led by Larry Wall. The Pugs |
|---|
| 42 | project |
|---|
| 43 | has been <a |
|---|
| 44 | href="http://www.nntp.perl.org/group/perl.perl6.language/19263">enthusiastically |
|---|
| 45 | welcomed</a> by the Perl 6 team.</p> |
|---|
| 46 | <h2> |
|---|
| 47 | Is Pugs the official Perl 6?</h2> |
|---|
| 48 | <p> |
|---|
| 49 | Official Perl 6 is now defined as any implementation which passes the |
|---|
| 50 | Perl 6 testsuite. So Pugs is expected to be an official Perl 6, but |
|---|
| 51 | not necessarily the only one.</p> |
|---|
| 52 | <h2> |
|---|
| 53 | Has Perl 6 been specified?</h2> |
|---|
| 54 | <p> |
|---|
| 55 | By December 2004, most of Perl 6 had |
|---|
| 56 | been |
|---|
| 57 | specified as a series of <a href="http://dev.perl.org/perl6/synopsis/">Synopses</a>. |
|---|
| 58 | Although not considered final, it is now stable enough to be |
|---|
| 59 | implemented. Many |
|---|
| 60 | of the Synopses are based on Larry's <a |
|---|
| 61 | href="http://dev.perl.org/perl6/apocalypse/">Apocalypses</a>. |
|---|
| 62 | Sometimes the |
|---|
| 63 | design team releases <a href="http://dev.perl.org/perl6/exegesis/">Exegeses</a>, |
|---|
| 64 | which explain the meaning of Apocalypses. Pugs adheres to |
|---|
| 65 | the Synopses, referring to Apocalypses or |
|---|
| 66 | Exegeses when a Synopsis is unclear or imprecise.</p> |
|---|
| 67 | <h2> |
|---|
| 68 | What does |
|---|
| 69 | “Apocrypha” mean?</h2> |
|---|
| 70 | <p> |
|---|
| 71 | The word <a href="http://en.wikipedia.org/wiki/Apocrypha">Apocrypha</a>, |
|---|
| 72 | from the Greek |
|---|
| 73 | απόκρυφος, |
|---|
| 74 | “hidden”, refers to religious works that are not |
|---|
| 75 | considered |
|---|
| 76 | canonical, or part of officially accepted scripture. The proper |
|---|
| 77 | singular form |
|---|
| 78 | in Greek is <i>Apocryphon</i>.</p> |
|---|
| 79 | <h2> |
|---|
| 80 | What is the relationship between |
|---|
| 81 | Apocrypha and the Perl 6 |
|---|
| 82 | design documents?</h2> |
|---|
| 83 | <p> |
|---|
| 84 | Apocalypses and Synopses cover the Perl |
|---|
| 85 | 6 |
|---|
| 86 | language in general; Apocrypha are specific to the Pugs implementation. |
|---|
| 87 | Like <a href="http://www.parrotcode.org/docs/pdd/">Parrot |
|---|
| 88 | Design Documents</a>, Apocrypha |
|---|
| 89 | will be constantly updated according to the status of Pugs.</p> |
|---|
| 90 | <h2> |
|---|
| 91 | Will Pugs implement the full Perl 6 |
|---|
| 92 | specification?</h2> |
|---|
| 93 | <p> |
|---|
| 94 | Yes. Pugs always targets the latest |
|---|
| 95 | revision of Perl 6 Synopses. As soon as a new revision or a new |
|---|
| 96 | Synopsis is published, |
|---|
| 97 | incompatibilities between Pugs and the new version will be considered |
|---|
| 98 | bugs in |
|---|
| 99 | Pugs.</p> |
|---|
| 100 | <h2> |
|---|
| 101 | Is Pugs free software?</h2> |
|---|
| 102 | <p> |
|---|
| 103 | Yes. It is available under the <a |
|---|
| 104 | href="http://svn.pugscode.org/pugs/LICENSE/Artistic-2">Artistic |
|---|
| 105 | License version 2.0</a>.</p> |
|---|
| 106 | <h2> |
|---|
| 107 | Is Pugs funded by the Perl Foundation?</h2> |
|---|
| 108 | <p> |
|---|
| 109 | No. After receiving three <a |
|---|
| 110 | href="http://www.perlfoundation.org/gc/grants/2003_autrijus.html">Perl |
|---|
| 111 | Foundation grants</a> on various |
|---|
| 112 | projects, Autrijus decides it would be more |
|---|
| 113 | helpful to donate time to the Perl 6 project by hacking Pugs, rather |
|---|
| 114 | than |
|---|
| 115 | asking TPF for money to do the same thing.</p> |
|---|
| 116 | <h2> |
|---|
| 117 | Where can I download Pugs?</h2> |
|---|
| 118 | <p> |
|---|
| 119 | For the very latest version of Pugs, |
|---|
| 120 | check |
|---|
| 121 | out the source from <a href="http://svn.pugscode.org/pugs/">Subversion</a> |
|---|
| 122 | or <a href="http://wagner.elixus.org/%7Eautrijus/darcs/pugs">darcs</a> |
|---|
| 123 | repositories. Periodic releases are available on CPAN |
|---|
| 124 | under the <a href="http://search.cpan.org/dist/Perl6-Pugs/">Perl6-Pugs</a> |
|---|
| 125 | namespace. |
|---|
| 126 | (By the way, if you'd like offline working with the Subversion |
|---|
| 127 | repository, the <a href="http://svk.elixus.org/">svk</a> |
|---|
| 128 | client may be of interest. But using |
|---|
| 129 | vanilla svn is fine.)</p> |
|---|
| 130 | <h2> |
|---|
| 131 | How do I build Pugs?</h2> |
|---|
| 132 | <p> |
|---|
| 133 | Pugs uses the standard Makefile.PL build |
|---|
| 134 | system, as detailed in the <a |
|---|
| 135 | href="http://svn.pugscode.org/pugs/README"><code>README</code></a> |
|---|
| 136 | file. Since Pugs is written in Haskell, you will need <a |
|---|
| 137 | href="http://haskell.org/ghc/">Glasgow Haskell |
|---|
| 138 | Compiler</a> (GHC) 6.4 or above. |
|---|
| 139 | Please download a <a href="http://haskell.org/ghc/">binary build</a> |
|---|
| 140 | for your |
|---|
| 141 | platform; compiling GHC from source code can take a very long time.</p> |
|---|
| 142 | <h2> |
|---|
| 143 | What is Haskell?</h2> |
|---|
| 144 | <p> |
|---|
| 145 | <a href="http://haskell.org/">Haskell</a> |
|---|
| 146 | is a standardized, purely functional programming language with |
|---|
| 147 | built-in <a href="http://en.wikipedia.org/wiki/Lazy_evaluation">lazy |
|---|
| 148 | evaluation</a> |
|---|
| 149 | capabilities. While there are several different implementations |
|---|
| 150 | available, |
|---|
| 151 | currently Pugs needs to be built with GHC, because it uses several |
|---|
| 152 | GHC-specific |
|---|
| 153 | features.</p> |
|---|
| 154 | <h2> |
|---|
| 155 | What is GHC?</h2> |
|---|
| 156 | <p> |
|---|
| 157 | GHC is a state-of-the-art compiler and |
|---|
| 158 | interactive |
|---|
| 159 | environment, available under a <a |
|---|
| 160 | href="http://haskell.org/ghc/license.html">BSD-style |
|---|
| 161 | license</a>. Itself written in |
|---|
| 162 | Haskell, GHC can compile Haskell to bytecode, C |
|---|
| 163 | code, and machine code on some platforms. GHC has an extensive library, |
|---|
| 164 | numerous language extensions, and a very capable optimizer (with some |
|---|
| 165 | help from |
|---|
| 166 | a <a |
|---|
| 167 | href="http://www.cse.unsw.edu.au/%7Echak/haskell/ghc/comm/the-beast/mangler.html">Perl |
|---|
| 168 | 5 program</a>). As such, it provides |
|---|
| 169 | an excellent platform to solve Perl 6’s <i>bootstrapping |
|---|
| 170 | problem</i>.</p> |
|---|
| 171 | <h2> |
|---|
| 172 | What is the Perl 6 bootstrapping problem?</h2> |
|---|
| 173 | <p> |
|---|
| 174 | The goal of the Perl 6 project is to be <i>self-hosting</i>: |
|---|
| 175 | The Perl 6 compiler needs to be written in Perl 6 itself, and must |
|---|
| 176 | parse Perl 6 |
|---|
| 177 | source code with Perl 6 Rules, which is a subset of the Perl 6 |
|---|
| 178 | language. The |
|---|
| 179 | generated code must also contain an evaluator that can execute Perl 6 |
|---|
| 180 | code on |
|---|
| 181 | the fly. The only way to break this cycle of dependency is by first |
|---|
| 182 | implementing some parts in other languages, then rewrite those parts in |
|---|
| 183 | Perl 6.</p> |
|---|
| 184 | <h2> |
|---|
| 185 | What was the initial bootstrapping plan?</h2> |
|---|
| 186 | <p> |
|---|
| 187 | According to the <a |
|---|
| 188 | href="http://search.cpan.org/dist/parrot/docs/faq.pod#Isn%27t_there_a_bootstrapping_problem?">Parrot |
|---|
| 189 | FAQ</a>, the initial plan was to |
|---|
| 190 | bootstrap via Perl 5: First we extend Perl 5 |
|---|
| 191 | to run on the Parrot virtual machine (via <code>B::Parrot</code> |
|---|
| 192 | or <a href="http://www.poniecode.org/">Ponie</a>), |
|---|
| 193 | and then implement the Perl 6 |
|---|
| 194 | compiler in Perl 5, which will be translated to Perl 6 via a p5-to-p6 |
|---|
| 195 | translator. However, although part of the Rule system was prototyped in |
|---|
| 196 | Perl 5 |
|---|
| 197 | as <a |
|---|
| 198 | href="http://search.cpan.org/dist/Perl6-Rules/"><code>Perl6::Rules</code></a>, |
|---|
| 199 | it was not mature enough to build a compiler on. As such, the plan was revised |
|---|
| 200 | to bootstrap via C instead.</p> |
|---|
| 201 | <h2> |
|---|
| 202 | What was the revised bootstrapping plan?</h2> |
|---|
| 203 | <p> |
|---|
| 204 | According to an early 2005 <a |
|---|
| 205 | href="http://www.perlfoundation.org/gc/grants/2005-p6-proposal.html">proposal</a>, |
|---|
| 206 | the plan is to first implement the Rule engine in C (i.e. <a |
|---|
| 207 | href="http://svn.perl.org/viewcvs/parrot/trunk/compilers/pge/">PGE</a>), |
|---|
| 208 | use it to parse Perl 6 into Parrot as an <a |
|---|
| 209 | href="http://en.wikipedia.org/wiki/Abstract_syntax_tree">abstract |
|---|
| 210 | syntax tree</a> |
|---|
| 211 | (AST), and then implement an AST evaluator as part of Parrot. Ponie and |
|---|
| 212 | p5-to-p6 are still in progress, but they are no longer critical |
|---|
| 213 | dependencies in |
|---|
| 214 | the |
|---|
| 215 | bootstrapping process.</p> |
|---|
| 216 | <h2> |
|---|
| 217 | How can Pugs help Perl 6 to bootstrap?</h2> |
|---|
| 218 | <p> |
|---|
| 219 | In a bootstrapping process, there are |
|---|
| 220 | often |
|---|
| 221 | many bottlenecks, which prevent people from working on things that |
|---|
| 222 | depend on |
|---|
| 223 | them. For example, one cannot easily write unit tests and standard |
|---|
| 224 | libraries |
|---|
| 225 | for Perl 6 without a working Perl 6 implementation, or work on an AST |
|---|
| 226 | evaluator |
|---|
| 227 | without an AST interface. Pugs solves such deadlocks by providing ready |
|---|
| 228 | substitutes |
|---|
| 229 | at various levels of the process.</p> |
|---|
| 230 | <h2> |
|---|
| 231 | How can Pugs help the Perl 6 language |
|---|
| 232 | design?</h2> |
|---|
| 233 | <p> |
|---|
| 234 | Without a working implementation, it is very hard to spot |
|---|
| 235 | inconsistencies and corner cases in the specification. |
|---|
| 236 | However, |
|---|
| 237 | if a design problem is found late into the implementation, it may |
|---|
| 238 | require |
|---|
| 239 | costly re-architecture for everything else. By providing a working Perl |
|---|
| 240 | 6 |
|---|
| 241 | implementation, Pugs can serve as a proving ground to resolve problems |
|---|
| 242 | as early |
|---|
| 243 | as possible, as well as encourage more people to exercise Perl |
|---|
| 244 | 6’s features.</p> |
|---|
| 245 | <h2> |
|---|
| 246 | Why did you choose Haskell?</h2> |
|---|
| 247 | <p> |
|---|
| 248 | Many Perl 6 features have similar |
|---|
| 249 | counterparts in Haskell: Perl 6 Rules corresponds closely to <a |
|---|
| 250 | href="http://www.cs.uu.nl/%7Edaan/download/parsec/parsec.html">Parsec</a>; |
|---|
| 251 | lazy |
|---|
| 252 | list evaluation is common in both languages; continuation support can |
|---|
| 253 | be |
|---|
| 254 | modeled with the <a |
|---|
| 255 | href="http://www.nomaware.com/monads/html/contmonad.html">ContT</a> |
|---|
| 256 | monad transformer, and so on. This greatly simplified the prototyping |
|---|
| 257 | effort: |
|---|
| 258 | the first working interpreter was released within the <a |
|---|
| 259 | href="http://use.perl.org/%7Eautrijus/journal/23051">first |
|---|
| 260 | week</a>, and by the <a |
|---|
| 261 | href="http://use.perl.org/%7Eautrijus/journal/23335">third |
|---|
| 262 | week</a> we had a full-fledged <a |
|---|
| 263 | href="http://svn.pugscode.org/pugs/ext/Test/lib/Test.pm"><code>Test.pm</code></a> |
|---|
| 264 | module for unit testing.</p> |
|---|
| 265 | <h2> |
|---|
| 266 | Is Pugs a compiler or an interpreter?</h2> |
|---|
| 267 | <p> |
|---|
| 268 | Similar to Perl 5, Pugs first compiles |
|---|
| 269 | Perl |
|---|
| 270 | 6 program to an AST, then executes it using the built-in evaluator. |
|---|
| 271 | However, in |
|---|
| 272 | the future Pugs may also provide a compiler interface that supports |
|---|
| 273 | different |
|---|
| 274 | compiler backends.</p> |
|---|
| 275 | <h2> |
|---|
| 276 | Which compiler backends do you have in |
|---|
| 277 | mind?</h2> |
|---|
| 278 | <p> |
|---|
| 279 | If implemented, the first compiler |
|---|
| 280 | backend |
|---|
| 281 | will likely generate Perl 6 code, similar to the <a |
|---|
| 282 | href="http://search.cpan.org/dist/perl/ext/B/B/Deparse.pm"><code>B::Deparse</code></a> |
|---|
| 283 | module. The next one may generate |
|---|
| 284 | Haskell code, which can then be |
|---|
| 285 | compiled to C by GHC. At that point, it may make sense to target the <a |
|---|
| 286 | href="http://svn.perl.org/viewcvs/parrot/trunk/compilers/ast/">Parrot |
|---|
| 287 | AST</a> |
|---|
| 288 | interface. We can also add other backends (such as Perl 5 bytecode) if |
|---|
| 289 | people |
|---|
| 290 | are willing to work on them.</p> |
|---|
| 291 | <h2> |
|---|
| 292 | Do you have a roadmap for Pugs |
|---|
| 293 | development?</h2> |
|---|
| 294 | <p> |
|---|
| 295 | The major/minor version numbers of Pugs |
|---|
| 296 | converges to 2*π; each significant digit in the minor version |
|---|
| 297 | represents a |
|---|
| 298 | milestone. The third digit is incremented for each release. The current |
|---|
| 299 | milestones are:</p> |
|---|
| 300 | <ul> |
|---|
| 301 | <li>6.0: Initial release.</li> |
|---|
| 302 | <li>6.2: Basic IO and control |
|---|
| 303 | flow |
|---|
| 304 | elements; mutable variables; assignment.</li> |
|---|
| 305 | <li>6.28: Classes and traits.</li> |
|---|
| 306 | <li>6.283: Rules and Grammars.</li> |
|---|
| 307 | <li>6.2831: Type system and linking.</li> |
|---|
| 308 | <li>6.28318: Macros.</li> |
|---|
| 309 | <li>6.283185: Port Pugs to |
|---|
| 310 | Perl 6, |
|---|
| 311 | if |
|---|
| 312 | needed.</li> |
|---|
| 313 | </ul> |
|---|
| 314 | <h2> |
|---|
| 315 | How portable is Pugs?</h2> |
|---|
| 316 | <p> |
|---|
| 317 | Pugs runs on Win32, Linux and many |
|---|
| 318 | flavors |
|---|
| 319 | of Unix systems. See GHC’s <a |
|---|
| 320 | href="http://haskell.org/ghc/contributors.html">porters |
|---|
| 321 | list</a> and <a href="http://haskell.org/ghc/download_ghc_622.html">download |
|---|
| 322 | page</a> for details. Starting from |
|---|
| 323 | 6.2.0, the Pugs team will also provide |
|---|
| 324 | binary builds on selected platforms.</p> |
|---|
| 325 | <h2> |
|---|
| 326 | How fast is Pugs?</h2> |
|---|
| 327 | <p> |
|---|
| 328 | The parser part of Pugs is very fast, |
|---|
| 329 | due |
|---|
| 330 | to its robust underpinning in Parsec. However, the Pugs evaluator is |
|---|
| 331 | currently |
|---|
| 332 | not optimized at all: dispatching is around 1000 operators per second |
|---|
| 333 | on a |
|---|
| 334 | typical PC, which is nearly 100 times slower than Perl 5. Still, it is |
|---|
| 335 | fast |
|---|
| 336 | enough for prototyping language features; if you need fast operations |
|---|
| 337 | in Pugs, |
|---|
| 338 | please consider helping out the Compiler backend.</p> |
|---|
| 339 | <h2> |
|---|
| 340 | Is there a CPAN for Perl 6 modules?</h2> |
|---|
| 341 | <p> |
|---|
| 342 | No. The current preferred method for submitting Perl 6/Pugs modules is to |
|---|
| 343 | ask for a committer bit at http://commitbit.pugscode.org/ and to add your |
|---|
| 344 | module to the Pugs source tree under the modules/ directory. It is also |
|---|
| 345 | helpful to include test suites with your modules as well, so we can know |
|---|
| 346 | when they work. |
|---|
| 347 | </P> |
|---|
| 348 | <P> |
|---|
| 349 | However, all is not lost. If you are patient you can wait for |
|---|
| 350 | <code>Pugs::MakeMaker</code> and <code>Module::Install::Pugs</code> to come out |
|---|
| 351 | on CPAN. Once they are available individually on CPAN, you can begin submitting |
|---|
| 352 | things to CPAN, because that means we've figured out the distribution problem. |
|---|
| 353 | Of course, suggestions are always welcome. |
|---|
| 354 | </p> |
|---|
| 355 | <h2> |
|---|
| 356 | Can Pugs work with Perl 5 libraries?</h2> |
|---|
| 357 | <p> |
|---|
| 358 | Yes, Pugs can work with Perl 5 libraries. This requires that Pugs be |
|---|
| 359 | compiled with Perl 5 embedding. Pugs understands Perl 5 objects, classes |
|---|
| 360 | and functions. Pugs objects, classes and functions are also understood by |
|---|
| 361 | Perl 5. As such, these types can be used in round-trip callbacks.</p> |
|---|
| 362 | |
|---|
| 363 | <p>Examples of working with Perl 5 may be found <a href="http://svn.pugscode.org/pugs/t/unspecced/p5/">in the source |
|---|
| 364 | tree</a>. |
|---|
| 365 | <h2> |
|---|
| 366 | Can Pugs work with Haskell libraries?</h2> |
|---|
| 367 | <p>Pugs can be compiled with <a |
|---|
| 368 | href="http://www.cse.unsw.edu.au/%7Edons/hs-plugins/"><code>hs-plugins</code></a> |
|---|
| 369 | support, which allows it to use Haskell libraries. It is also capable of |
|---|
| 370 | dynamically loading Haskell modules. Aside from this, inline Haskell can |
|---|
| 371 | be evaluated using <code>eval('...', :lang<haskell>)</code>.</p> |
|---|
| 372 | <p>In addition, at the basic level, you can statically link Haskell libraries |
|---|
| 373 | into Pugs primitives, by modifying a few lines in <a |
|---|
| 374 | href="http://svn.pugscode.org/pugs/src/Pugs/Prim.hs"><code>Prim.hs</code></a>. |
|---|
| 375 | </p> |
|---|
| 376 | <h2> |
|---|
| 377 | Can Pugs work with C libraries?</h2> |
|---|
| 378 | <p> |
|---|
| 379 | Not yet. However, <a href="http://www.haskell.org/hdirect/">HaskellDirect</a> |
|---|
| 380 | seems to provide an |
|---|
| 381 | easy way to interface with C, CORBA and COM libraries, especially when |
|---|
| 382 | combined |
|---|
| 383 | with hs-plugins described above.</p> |
|---|
| 384 | <h2> |
|---|
| 385 | I know Perl 5, but not Haskell. Can I |
|---|
| 386 | develop Pugs?</h2> |
|---|
| 387 | <p> |
|---|
| 388 | Sure! The standard libraries and unit |
|---|
| 389 | tests |
|---|
| 390 | that come with Pugs are coded in Perl 6, and there is always a need for |
|---|
| 391 | more |
|---|
| 392 | tests and libraries. All you need is basic familiarity of Perl 5, and a |
|---|
| 393 | few |
|---|
| 394 | minutes to get acquainted with some small syntax changes. You will |
|---|
| 395 | likely pick |
|---|
| 396 | up some Haskell knowledge along the way, too.</p> |
|---|
| 397 | <h2> |
|---|
| 398 | I know Haskell, but not Perl 5. Can I |
|---|
| 399 | develop Pugs?</h2> |
|---|
| 400 | <p> |
|---|
| 401 | Sure! Perl 6 and Haskell have many |
|---|
| 402 | things |
|---|
| 403 | in common, such as type-based function dispatch, first class functions |
|---|
| 404 | and |
|---|
| 405 | currying, so picking up the syntax is relatively easy. Since there are |
|---|
| 406 | always |
|---|
| 407 | some TODO tests for features in need of implementation, it is never |
|---|
| 408 | hard to |
|---|
| 409 | find something to do.</p> |
|---|
| 410 | <h2> |
|---|
| 411 | I have learned some Perl 6. What can I |
|---|
| 412 | do with Pugs?</h2> |
|---|
| 413 | <p> |
|---|
| 414 | Look at the examples/ directory to see |
|---|
| 415 | some |
|---|
| 416 | sample programs. Some people are already writing web applications and |
|---|
| 417 | report |
|---|
| 418 | systems with Pugs. If you run into a missing feature in Pugs, please |
|---|
| 419 | let us |
|---|
| 420 | know so we can implement it.</p> |
|---|
| 421 | <h2> |
|---|
| 422 | Where can I learn more about Haskell?</h2> |
|---|
| 423 | <p> |
|---|
| 424 | The <a href="http://www.haskell.org/">Haskell |
|---|
| 425 | homepage</a> and the <a href="http://haskell.org/hawiki/">Wiki</a> |
|---|
| 426 | are good |
|---|
| 427 | entry points. Of the many online tutorials, <a |
|---|
| 428 | href="http://www.isi.edu/%7Ehdaume/htut/">Yet Another |
|---|
| 429 | Haskell Tutorial</a> is |
|---|
| 430 | perhaps the most accessible. Due to the ubiquitous use of Monad |
|---|
| 431 | transformers in |
|---|
| 432 | Pugs, <a href="http://www.nomaware.com/monads/html/">All About |
|---|
| 433 | Monads</a> is |
|---|
| 434 | also recommended. For books, <a |
|---|
| 435 | href="http://www.iro.umontreal.ca/%7Elapalme/Algorithms-functional.html">Algorithms: |
|---|
| 436 | A Functional Programming Approach</a>, |
|---|
| 437 | <a href="http://www.cs.kent.ac.uk/people/staff/sjt/craft2e/">Haskell: |
|---|
| 438 | The Craft of |
|---|
| 439 | Functional Programming</a> and <a href="http://haskell.org/soe/">The |
|---|
| 440 | Haskell School of |
|---|
| 441 | Expression</a> |
|---|
| 442 | are |
|---|
| 443 | fine introductory materials. Finally, the |
|---|
| 444 | <a href="irc://irc.freenode.net/haskell"><code>#haskell</code> channel</a> on |
|---|
| 445 | <a href="http://freenode.net/">irc.freenode.net</a> is full of helpful and |
|---|
| 446 | interesting people.</p> |
|---|
| 447 | <h2> |
|---|
| 448 | Where can I learn more about Perl 6?</h2> |
|---|
| 449 | <p> |
|---|
| 450 | The <a href="http://dev.perl.org/perl6/">Perl |
|---|
| 451 | 6 homepage</a> provides many online |
|---|
| 452 | documents. Every week or two, a new Perl 6 |
|---|
| 453 | list summary will appear on <a href="http://www.perl.com/">Perl.com</a>; |
|---|
| 454 | it is |
|---|
| 455 | a must-read for people who wish to follow Perl 6’s progress. |
|---|
| 456 | For books, <a href="http://www.oreilly.com/catalog/059600737X/">Perl |
|---|
| 457 | 6 and Parrot Essentials</a> |
|---|
| 458 | and <a href="http://www.apress.com/book/bookDisplay.html?bID=355">Perl |
|---|
| 459 | 6 Now</a> |
|---|
| 460 | are both helpful.</p> |
|---|
| 461 | <h2> |
|---|
| 462 | Where can I learn more about |
|---|
| 463 | implementing programming |
|---|
| 464 | languages?</h2> |
|---|
| 465 | <p> |
|---|
| 466 | <a href="http://www.cis.upenn.edu/%7Ebcpierce/tapl/">Types |
|---|
| 467 | and Programming Languages</a> |
|---|
| 468 | is an essential read; Pugs started out as a self-initiated study of the |
|---|
| 469 | text, |
|---|
| 470 | and it continues to be an important guide during the implementation. |
|---|
| 471 | Its |
|---|
| 472 | sequel, <a href="http://www.cis.upenn.edu/%7Ebcpierce/attapl/">Advanced |
|---|
| 473 | Topics in |
|---|
| 474 | Types and Programming Languages</a>, |
|---|
| 475 | is also invaluable. It may also help to |
|---|
| 476 | get acquainted with other multi-paradigmatic languages, such as <a |
|---|
| 477 | href="http://www.mozart-oz.org/">Mozart/Oz</a>, |
|---|
| 478 | <a href="http://www.informatik.uni-kiel.de/%7Emh/curry/">Curry</a> |
|---|
| 479 | and <a href="http://www.ocaml.org/">O’Caml</a>. |
|---|
| 480 | Finally, the detailed <a |
|---|
| 481 | href="http://www.cse.unsw.edu.au/%7Echak/haskell/ghc/comm/">GHC |
|---|
| 482 | commentary</a> |
|---|
| 483 | describes how GHC itself was implemented.</p> |
|---|
| 484 | <h2> |
|---|
| 485 | I’d like to help. What should |
|---|
| 486 | I do?</h2> |
|---|
| 487 | <p> |
|---|
| 488 | First, subscribe to the <a |
|---|
| 489 | href="http://nntp.perl.org/group/perl.perl6.compiler">perl6-compiler</a> |
|---|
| 490 | mailing list by sending an empty mail to <a |
|---|
| 491 | href="mailto:perl6-compiler-subscribe@perl.org">perl6-compiler-subscribe@perl.org</a>. |
|---|
| 492 | Next, join the <a href="irc://irc.freenode.net/perl6"><code>#perl6</code> |
|---|
| 493 | IRC channel</a> on <a href="http://freenode.net/">irc.freenode.net</a> to find out what needs to be done. Commit |
|---|
| 494 | access is handed out liberally; contact the Pugs team on <code>#perl6</code> |
|---|
| 495 | for details. See you on IRC!</p> |
|---|
| 496 | </body> |
|---|
| 497 | </html> |
|---|
