Changeset 7843 for docs/AES/S22draft.pod

Timestamp:

11/05/05 11:41:57 (3 years ago)

Author:

autrijus

Message:

[Massive backport from svn.perl.org now openfoundry is back]

* theorbtwo notes that FIRST {} blocks did not

desugar into anything that passes PIL compilation,
as it's useing a Stmt in LValue position.
Fixed by desugaring using ternary if.

* Squash an empty import warning for precompiled preludes.

* Support for "./pugs -C PIL2".

Currently, "-C PIL" and "-C PIL1" both maps to PIL1,
but some day "-C PIL" may change to PIL2.

* Repo copy Pugs.CodeGen?.PIL to Pugs.CodeGen?.PIL2
* Also rename CodeGen?.PIL to CodeGen?.PIL1

* Add DrIFT-generated source of PIL2.hs.

* Repo copy PIL1 to PIL2 for the long-much-overdue PIL2

refactoring. The goals are:

• Compile time object serialization
• Lexical hoisting
• Static creation of Code objects with scope (no PSub forms)
• Full Cxt information
• PIL2 is *after* type erasure -- *no* static type annotation should be left after that -- it's somewhere between F<: and ANF, so to speak.

* Adds support for "./pugs -BPugs -e ...", which just takes

-CPugs output and feed to the "runghc" executable in PATH.

* pugscc: chase the s/MainCC.mainCC/Main.main/ change

as the now-cabalized Pugs package no longer exports "main".

* Compile-time objects now survives "./pugs -CPugs" compilation.

This means the line below works now:

pugscc -e 'class F {}; my $x ::= F.new; say $x'

Previously, the ::= would prevent compilation because we
did not have a serialization protocol for VObject types.
(This work is going to be carried over to PIL.)

Files:

• docs/AES/S22draft.pod (modified) (5 diffs)

docs/AES/S22draft.pod

@@ -9 +9 @@
 Jos Boumans <kane@cpan.org>
 Autrijus Tang <autrijus@autrijus.org>
-Florian Ragwitz <rafl@debian.org>
 
 =head1 VERSION
@@ -24 +23 @@
 
 'package management means several things':
-    - metadata collection                           (1) perl6-thingy or maybe debtags?
+    - metadata collection                           (1) perl6-thingy
     - package building                              (2) make dist
         - intermediate format for transport
@@ -30 +29 @@
             - decomposed to hooks and probes
         - uploading package to central area         (3) CPAN
-        - indexing                                  (4) apt-ftparchive
-                    - I don't think apt-ftparchive is enough here. I think we'll need to set up
-                          or even wright something like dak, the Debian archive maintaince scripts
-                          packages.debian.org/dak
-        - understanding/querying index              (5) apt-cache, debtags
+        - indexing                                  (4) aptftp-archive
+        - understanding/querying index              (5) apt-cache
         - fetching package
         - building final package                    (6) dpkg-deb
@@ -116 +112 @@
 
 =head3 Repositories
-
-My ideas for the repository layout look like this. It's modeled after the
-Debian archive structure.
-
- /
- |- dists/                  This directory only contains so called Packages files.
- |  |                       They know some meta-information about the packages (description, ...)
- |  |                       and a path to the real package inside pool/. Using this Packages
- |  |                       files modules can be categorized very well. There are more then the
- |  |                       showed categories possible, of course. It's only an example.
- |  |
- |  |- authors/             The whole archive sorted by authors
- |  |  |- stevan.gz         Stevan's modules
- |  |  |- autrijus.gz       All of autrijus modules
- |  |  |- autrijus/
- |  |  |  |- Perl6-Pugs.gz  Individual modules
- |  |  |  `- Acme-Hello.gz
- |  |  `- rafl.gz           rafl's modules.
- |  |
- |  |- languages/           The archive sorted by language
- |  |  |- perl.gz           All available perl modules
- |  |  |- perl/
- |  |  |  |- kane.gz        kane's modules
- |  |  |  `- gbarr.gz       gbarr's modules
- |  |  |- js.gz             All js modules
- |  |  |- js/
- |  |  |- ruby.gz
- |  |  `- ruby/             Ruby stuff
- |  |
- |  `- modules/             Categorized by modules
- |     |- DBI/
- |     |  |- timb.gz        Tim's DBI
- |     |  `- rafl.gz        My DBI
- |     |- Net-SMTP/
- |     `- Net-IMCP/
- |
- `- pool/                       The real modules are stored here. The Packages files point here.
-    |- a/                       Modules startihg with 'a'
-    |  |- Acme-Foo/             All Acme-Foo versions
-    |  |  |- Acme-Foo-0.1.deb   Packages for specific Acme-Foo versions
-    |  |  `- Acme-Foo-0.2.deb
-    |  |- Acme-Bar/
-    |  `- Acme-Hello/
-    |- b/
-    |- c/
-    |- ./
-    |- ./
-    |- ./
-    |- y/
-    `- z/
 
 =head3 Probing
@@ -261 +207 @@
             - without which we can't possibly roll this out
 
-rafl thinks:
-- dpkg seems to be not the optimal choice
-    - maybe only adopt the package and metadata format from the .deb format version 2
-          and write the tools to manipulate and install it ourself. Preferably in Perl 6.
-        - I fear that tools like dpkg/apt/.. aren't portable as we need it because they
-          were mainly written for use with a single Linux distribution.
-        - The Debian tools can be useful as a provisional solutions until we wrote
-          something own or as a reference implementation.
-
 =head2 Policy File