pygments.rb 0.6.3 → 1.0.0

data/vendor/pygments-main/doc/docs/lexers.rst

@@ -27,11 +27,11 @@ Currently, **all lexers** support these options:
 `encoding`
     If given, must be an encoding name (such as ``"utf-8"``). This encoding
     will be used to convert the input string to Unicode (if it is not already
-    a Unicode string). The default is ``"latin1"``.
+    a Unicode string). The default is ``"guess"``.
 
     If this option is set to ``"guess"``, a simple UTF-8 vs. Latin-1
     detection is used, if it is set to ``"chardet"``, the
-    `chardet library <http://chardet.feedparser.org/>`__ is used to
+    `chardet library <https://chardet.github.io/>`_ is used to
     guess the encoding of the input.
 
     .. versionadded:: 0.6

data/vendor/pygments-main/doc/docs/styles.rst

@@ -21,6 +21,7 @@ option in form of a string:
 .. sourcecode:: pycon
 
     >>> from pygments.styles import get_style_by_name
+    >>> from pygments.formatters import HtmlFormatter
     >>> HtmlFormatter(style='colorful').style
     <class 'pygments.styles.colorful.ColorfulStyle'>
 
@@ -30,6 +31,7 @@ Or you can also import your own style (which must be a subclass of
 .. sourcecode:: pycon
 
     >>> from yourapp.yourmodule import YourStyle
+    >>> from pygments.formatters import HtmlFormatter
     >>> HtmlFormatter(style=YourStyle).style
     <class 'yourapp.yourmodule.YourStyle'>
 
@@ -141,3 +143,59 @@ a way to iterate over all styles:
 
     >>> from pygments.styles import get_all_styles
     >>> styles = list(get_all_styles())
+
+
+.. _AnsiTerminalStyle:
+
+Terminal Styles
+===============
+
+.. versionadded:: 2.2
+
+Custom styles used with the 256-color terminal formatter can also map colors to
+use the 8 default ANSI colors.  To do so, use ``#ansigreen``, ``#ansired`` or
+any other colors defined in :attr:`pygments.style.ansicolors`.  Foreground ANSI
+colors will be mapped to the corresponding `escape codes 30 to 37
+<https://en.wikipedia.org/wiki/ANSI_escape_code#Colors>`_ thus respecting any
+custom color mapping and themes provided by many terminal emulators.  Light
+variants are treated as foreground color with and an added bold flag.
+``bg:#ansi<color>`` will also be respected, except the light variant will be the
+same shade as their dark variant.
+
+See the following example where the color of the string ``"hello world"`` is
+governed by the escape sequence ``\x1b[34;01m`` (Ansi Blue, Bold, 41 being red
+background) instead of an extended foreground & background color.
+
+.. sourcecode:: pycon
+
+    >>> from pygments import highlight
+    >>> from pygments.style import Style
+    >>> from pygments.token import Token
+    >>> from pygments.lexers import Python3Lexer
+    >>> from pygments.formatters import Terminal256Formatter
+
+    >>> class MyStyle(Style):
+            styles = {
+                Token.String:     '#ansiblue bg:#ansired',
+            }
+
+    >>> code = 'print("Hello World")'
+    >>> result = highlight(code, Python3Lexer(), Terminal256Formatter(style=MyStyle))
+    >>> print(result.encode())
+    b'\x1b[34;41;01m"\x1b[39;49;00m\x1b[34;41;01mHello World\x1b[39;49;00m\x1b[34;41;01m"\x1b[39;49;00m'
+
+Colors specified using ``#ansi*`` are converted to a default set of RGB colors
+when used with formatters other than the terminal-256 formatter.
+
+By definition of ANSI, the following colors are considered "light" colors, and
+will be rendered by most terminals as bold:
+
+- "darkgray", "red", "green", "yellow", "blue", "fuchsia", "turquoise", "white"
+
+The following are considered "dark" colors and will be rendered as non-bold:
+
+- "black", "darkred", "darkgreen", "brown", "darkblue", "purple", "teal",
+  "lightgray"
+
+Exact behavior might depends on the terminal emulator you are using, and its
+settings.

data/vendor/pygments-main/doc/docs/tokens.rst

@@ -89,7 +89,7 @@ The `is_token_subtype()` function in the `pygments.token` module can be used to
 test if a token type is a subtype of another (such as `Name.Tag` and `Name`).
 (This is the same as ``Name.Tag in Name``. The overloaded `in` operator was newly
 introduced in Pygments 0.7, the function still exists for backwards
-compatiblity.)
+compatibility.)
 
 With Pygments 0.7, it's also possible to convert strings to token types (for example
 if you want to supply a token from the command line):
@@ -160,7 +160,7 @@ Name Tokens
     other languages constants are uppercase by definition (Ruby).
 
 `Name.Decorator`
-    Token type for decorators. Decorators are synatic elements in the Python
+    Token type for decorators. Decorators are syntactic elements in the Python
     language. Similar syntax elements exist in C# and Java.
 
 `Name.Entity`
@@ -174,6 +174,10 @@ Name Tokens
 `Name.Function`
     Token type for function names.
 
+`Name.Function.Magic`
+    same as `Name.Function` but for special function names that have an implicit use
+    in a language (e.g. ``__init__`` method in Python).
+
 `Name.Label`
     Token type for label names (e.g. in languages that support ``goto``).
 
@@ -201,6 +205,10 @@ Name Tokens
 `Name.Variable.Instance`
     same as `Name.Variable` but for instance variables.
 
+`Name.Variable.Magic`
+    same as `Name.Variable` but for special variable names that have an implicit use
+    in a language (e.g. ``__doc__`` in Python).
+
 
 Literals
 ========
@@ -215,12 +223,20 @@ Literals
 `String`
     For any string literal.
 
+`String.Affix`
+    Token type for affixes that further specify the type of the string they're
+    attached to (e.g. the prefixes ``r`` and ``u8`` in ``r"foo"`` and ``u8"foo"``). 
+
 `String.Backtick`
     Token type for strings enclosed in backticks.
 
 `String.Char`
     Token type for single characters (e.g. Java, C).
 
+`String.Delimiter`
+    Token type for delimiting identifiers in "heredoc", raw and other similar
+    strings (e.g. the word ``END`` in Perl code ``print <<'END';``).
+
 `String.Doc`
     Token type for documentation strings (for example Python).
 
@@ -297,6 +313,10 @@ Comments
 `Comment`
     Token type for any comment.
 
+`Comment.Hashbang`
+    Token type for hashbang comments (i.e. first lines of files that start with
+     ``#!``).
+
 `Comment.Multiline`
     Token type for multiline comments.
 

data/vendor/pygments-main/doc/docs/unicode.rst

@@ -6,12 +6,20 @@ Since Pygments 0.6, all lexers use unicode strings internally. Because of that
 you might encounter the occasional :exc:`UnicodeDecodeError` if you pass strings
 with the wrong encoding.
 
-Per default all lexers have their input encoding set to `latin1`.
-If you pass a lexer a string object (not unicode), it tries to decode the data
-using this encoding.
-You can override the encoding using the `encoding` lexer option. If you have the
-`chardet`_ library installed and set the encoding to ``chardet`` if will ananlyse
-the text and use the encoding it thinks is the right one automatically:
+Per default all lexers have their input encoding set to `guess`.  This means
+that the following encodings are tried:
+
+* UTF-8 (including BOM handling)
+* The locale encoding (i.e. the result of `locale.getpreferredencoding()`)
+* As a last resort, `latin1`
+
+If you pass a lexer a byte string object (not unicode), it tries to decode the
+data using this encoding.
+
+You can override the encoding using the `encoding` or `inencoding` lexer
+options.  If you have the `chardet`_ library installed and set the encoding to
+``chardet`` if will analyse the text and use the encoding it thinks is the
+right one automatically:
 
 .. sourcecode:: python
 
@@ -47,4 +55,4 @@ encoding is handled differently, see :doc:`the command line docs <cmdline>`.
    options dict with lexers and formatters, and still have different input and
    output encodings.
 
-.. _chardet: http://chardet.feedparser.org/
+.. _chardet: https://chardet.github.io/

data/vendor/pygments-main/doc/faq.rst

@@ -12,8 +12,7 @@ processed version (in different formats) containing syntax highlighting markup.
 
 Its features include:
 
-* a wide range of common languages and markup formats is supported (look here
-  for a list)
+* a wide range of common :doc:`languages and markup formats <languages>` is supported
 * new languages and formats are added easily
 * a number of output formats is available, including:
 
@@ -58,7 +57,7 @@ Usage as a library is thoroughly demonstrated in the Documentation section.
 How do I make a new style?
 --------------------------
 
-Please see the documentation on styles.
+Please see the :doc:`documentation on styles <docs/styles>`.
 
 How can I report a bug or suggest a feature?
 --------------------------------------------
@@ -90,29 +89,24 @@ Who uses Pygments?
 
 This is an (incomplete) list of projects and sites known to use the Pygments highlighter.
 
-* `Pygments API <http://pygments.appspot.com/>`_, a HTTP POST interface to Pygments
+* `Wikipedia <http://en.wikipedia.org>`_
+* `BitBucket <http://bitbucket.org/>`_, a Mercurial and Git hosting site
 * `The Sphinx documentation builder <http://sphinx.pocoo.org/>`_, for embedded source examples
 * `rst2pdf <http://code.google.com/p/rst2pdf/>`_, a reStructuredText to PDF converter
-* `Zine <http://zine.pocoo.org/>`_, a Python blogging system
+* `Codecov <http://codecov.io/>`_, a code coverage CI service
 * `Trac <http://trac.edgewall.org/>`_, the universal project management tool
-* `Bruce <http://r1chardj0n3s.googlepages.com/bruce>`_, a reStructuredText presentation tool
 * `AsciiDoc <http://www.methods.co.nz/asciidoc/>`_, a text-based documentation generator
 * `ActiveState Code <http://code.activestate.com/>`_, the Python Cookbook successor
 * `ViewVC <http://viewvc.org/>`_, a web-based version control repository browser
 * `BzrFruit <http://repo.or.cz/w/bzrfruit.git>`_, a Bazaar branch viewer
 * `QBzr <http://bazaar-vcs.org/QBzr>`_, a cross-platform Qt-based GUI front end for Bazaar
-* `BitBucket <http://bitbucket.org/>`_, a Mercurial and Git hosting site
-* `GitHub <http://github.com/>`_, a site offering secure Git hosting and collaborative development
 * `Review Board <http://www.review-board.org/>`_, a collaborative code reviewing tool
-* `skeletonz <http://orangoo.com/skeletonz/>`_, a Python powered content management system
 * `Diamanda <http://code.google.com/p/diamanda/>`_, a Django powered wiki system with support for Pygments
 * `Progopedia <http://progopedia.ru/>`_ (`English <http://progopedia.com/>`_),
   an encyclopedia of programming languages
-* `Postmarkup <http://code.google.com/p/postmarkup/>`_, a BBCode to XHTML generator
-* `Language Comparison <http://michaelsilver.us/lc>`_, a site that compares different programming languages
-* `BPython <http://www.noiseforfree.com/bpython/>`_, a curses-based intelligent Python shell
-* `Challenge-You! <http://challenge-you.appspot.com/>`_, a site offering programming challenges
+* `Bruce <http://r1chardj0n3s.googlepages.com/bruce>`_, a reStructuredText presentation tool
 * `PIDA <http://pida.co.uk/>`_, a universal IDE written in Python
+* `BPython <http://www.noiseforfree.com/bpython/>`_, a curses-based intelligent Python shell
 * `PuDB <http://pypi.python.org/pypi/pudb>`_, a console Python debugger
 * `XWiki <http://www.xwiki.org/>`_, a wiki-based development framework in Java, using Jython
 * `roux <http://ananelson.com/software/roux/>`_, a script for running R scripts
@@ -120,23 +114,25 @@ This is an (incomplete) list of projects and sites known to use the Pygments hig
 * `hurl <http://hurl.it/>`_, a web service for making HTTP requests
 * `wxHTMLPygmentizer <http://colinbarnette.net/projects/wxHTMLPygmentizer>`_ is
   a GUI utility, used to make code-colorization easier
-* `WpPygments <http://blog.mirotin.net/?page_id=49>`_, a highlighter plugin for WordPress
-* `LodgeIt <http://paste.pocoo.org/>`_, a pastebin with XMLRPC support and diffs
-* `SpammCan <http://chrisarndt.de/projects/spammcan/>`_, a pastebin (demo see
-  `here <http://paste.chrisarndt.de/>`_)
-* `WowAce.com pastes <http://www.wowace.com/paste/>`_, a pastebin
+* `Postmarkup <http://code.google.com/p/postmarkup/>`_, a BBCode to XHTML generator
+* `WpPygments <http://blog.mirotin.net/?page_id=49>`_, and `WPygments
+  <https://github.com/capynet/WPygments>`_, highlighter plugins for WordPress
 * `Siafoo <http://siafoo.net>`_, a tool for sharing and storing useful code and programming experience
 * `D source <http://www.dsource.org/>`_, a community for the D programming language
-* `dumpz.org <http://dumpz.org/>`_, a pastebin
 * `dpaste.com <http://dpaste.com/>`_, another Django pastebin
-* `PylonsHQ Pasties <http://pylonshq.com/pasties/new>`_, a pastebin
 * `Django snippets <http://www.djangosnippets.org/>`_, a pastebin for Django code
 * `Fayaa <http://www.fayaa.com/code/>`_, a Chinese pastebin
 * `Incollo.com <http://incollo.com>`_, a free collaborative debugging tool
 * `PasteBox <http://p.boxnet.eu/>`_, a pastebin focused on privacy
-* `xinotes.org <http://www.xinotes.org/>`_, a site to share notes, code snippets etc.
 * `hilite.me <http://www.hilite.me/>`_, a site to highlight code snippets
 * `patx.me <http://patx.me/paste>`_, a pastebin
+* `Fluidic <https://github.com/richsmith/fluidic>`_, an experiment in
+  integrating shells with a GUI
+* `pygments.rb <https://github.com/tmm1/pygments.rb>`_, a pygments wrapper for Ruby
+* `Clygments <https://github.com/bfontaine/clygments>`_, a pygments wrapper for
+  Clojure
+* `PHPygments <https://github.com/capynet/PHPygments>`_, a pygments wrapper for PHP
+
 
 If you have a project or web site using Pygments, drop me a line, and I'll add a
 link here.

data/vendor/pygments-main/doc/index.rst

@@ -1,20 +1,21 @@
 Welcome!
 ========
 
-This is the home of Pygments. It is a generic syntax highlighter for general use
-in all kinds of software such as forum systems, wikis or other applications that
-need to prettify source code. Highlights are:
+This is the home of Pygments.  It is a generic syntax highlighter suitable for
+use in code hosting, forums, wikis or other applications that need to prettify
+source code.  Highlights are:
 
-* a wide range of common languages and markup formats is supported
+* a wide range of over 300 languages and other text formats is supported
 * special attention is paid to details that increase highlighting quality
-* support for new languages and formats are added easily; most languages use a simple regex-based lexing mechanism
-* a number of output formats is available, among them HTML, RTF, LaTeX and ANSI sequences
+* support for new languages and formats are added easily; most languages use a
+  simple regex-based lexing mechanism
+* a number of output formats is available, among them HTML, RTF, LaTeX and ANSI
+  sequences
 * it is usable as a command-line tool and as a library
-* ... and it highlights even Brainf*ck!
+* ... and it highlights even Perl 6!
 
-Read more in the FAQ list or the documentation, or download the latest release.
-
-Though Pygments has not yet won an award, we trust that you will notice it's a top quality product <wink>.
+Read more in the :doc:`FAQ list <faq>` or the :doc:`documentation <docs/index>`,
+or `download the latest release <http://pypi.python.org/pypi/Pygments>`_.
 
 .. _contribute:
 
@@ -45,7 +46,7 @@ Pygments is maintained by **Georg Brandl**, e-mail address *georg*\ *@*\ *python
 
 Many lexers and fixes have been contributed by **Armin Ronacher**, the rest of
 the `Pocoo <http://dev.pocoo.org/>`_ team and **Tim Hatch**.
- 
+
 .. toctree::
    :maxdepth: 1
    :hidden:

data/vendor/pygments-main/doc/languages.rst

@@ -26,12 +26,15 @@ Programming languages
 * Common Lisp
 * Coq
 * Cryptol (incl. Literate Cryptol)
+* `Crystal <http://crystal-lang.org>`_
 * `Cython <http://cython.org>`_
-* `D <http://digitalmars.com/d>`_
+* `D <http://dlang.org>`_
 * Dart
 * Delphi
 * Dylan
+* `Elm <http://elm-lang.org/>`_
 * Erlang
+* `Ezhil <http://ezhillang.org>`_ Ezhil - A Tamil programming language
 * Factor
 * Fancy
 * Fortran
@@ -45,6 +48,7 @@ Programming languages
 * Io
 * Java
 * JavaScript
+* Lasso
 * LLVM
 * Logtalk
 * `Lua <http://www.lua.org>`_
@@ -85,7 +89,6 @@ Programming languages
 * Visual FoxPro
 * XQuery
 * Zephir
-  </ul>
 
 Template languages
 ------------------
@@ -97,8 +100,8 @@ Template languages
 * `Genshi <http://genshi.edgewall.org>`_ (the Trac template language)
 * JSP (Java Server Pages)
 * `Myghty <http://www.myghty.org>`_ (the HTML::Mason based framework)
-* `Mako <http://www.makotemplates.org/>`_ (the Myghty successor)
-* `Smarty <http://smarty.php.net>`_ templates (PHP templating)
+* `Mako <http://www.makotemplates.org>`_ (the Myghty successor)
+* `Smarty <http://www.smarty.net>`_ templates (PHP templating)
 * Tea
 
 Other markup
@@ -143,9 +146,9 @@ Other markup
 ... that's all?
 ---------------
 
-Well, why not write your own? Contributing to Pygments is easy and fun.  Look
-:doc:`here <docs/lexerdevelopment>` for the docs on lexer development and
-:ref:`here <contribute>` for contact details.
+Well, why not write your own? Contributing to Pygments is easy and fun.  Take a look at the
+:doc:`docs on lexer development <docs/lexerdevelopment>` and
+:ref:`contact details <contribute>`.
 
 Note: the languages listed here are supported in the development version. The
 latest release may lack a few of them.

data/vendor/pygments-main/external/autopygmentize

@@ -1,6 +1,6 @@
 #!/bin/bash
 # Best effort auto-pygmentization with transparent decompression
-# (c) Reuben Thomas 2012-2013
+# by Reuben Thomas 2008-2015
 # This program is in the public domain.
 
 # Strategy: first see if pygmentize can find a lexer; if not, ask file; if that finds nothing, fail
@@ -18,6 +18,7 @@ if [[ "$lexer" == text ]]; then
     unset lexer
     case $(file --mime-type --uncompress $file_common_opts "$file") in
         application/xml|image/svg+xml) lexer=xml;;
+        application/javascript) lexer=javascript;;
         text/html) lexer=html;;
         text/troff) lexer=nroff;;
         text/x-asm) lexer=nasm;;
@@ -39,15 +40,18 @@ if [[ "$lexer" == text ]]; then
         text/x-po) lexer=po;;
         text/x-python) lexer=python;;
         text/x-ruby) lexer=ruby;;
+        text/x-crystal) lexer=crystal;;
         text/x-shellscript) lexer=sh;;
         text/x-tcl) lexer=tcl;;
         text/x-tex|text/x-texinfo) lexer=latex;; # FIXME: texinfo really needs its own lexer
         
-        # Types that file outputs which pygmentize didn't support as of file 5.11, pygments 1.6rc1
+        # Types that file outputs which pygmentize didn't support as of file 5.20, pygments 2.0
         # text/calendar
+        # text/inf
         # text/PGP
         # text/rtf
         # text/texmacs
+        # text/vnd.graphviz
         # text/x-bcpl
         # text/x-info
         # text/x-m4
@@ -63,8 +67,8 @@ if [[ "$lexer" == text ]]; then
 fi
 
 encoding=$(file --mime-encoding --uncompress $file_common_opts "$file")
-if [[ $encoding == "us-asciibinarybinary" ]]; then
-	encoding="us-ascii"
+if [[ $encoding == "binary" ]]; then
+    encoding="latin1"
 fi
 
 if [[ -n "$lexer" ]]; then
@@ -74,8 +78,7 @@ if [[ -n "$lexer" ]]; then
         application/x-bzip2) concat=bzcat;;
         application/x-xz)    concat=xzcat;;
     esac
-    # FIXME: Specify input encoding rather than output encoding https://bitbucket.org/birkenfeld/pygments-main/issue/800
-    exec $concat "$file" | pygmentize -f terminal256 -O style=native,encoding=$encoding,outencoding=UTF-8 $PYGMENTIZE_OPTS $options -l $lexer
+    exec $concat "$file" | pygmentize -O inencoding=$encoding $PYGMENTIZE_OPTS $options -l $lexer
 fi
 
 exit 1

data/vendor/pygments-main/external/lasso-builtins-generator-9.lasso

@@ -4,9 +4,9 @@
 	Builtins Generator for Lasso 9
 
 	This is the shell script that was used to extract Lasso 9's built-in keywords
-	and generate most of the _lassobuiltins.py file. When run, it creates a file
-	named "lassobuiltins-9.py" containing the types, traits, methods, and members
-	of the currently-installed version of Lasso 9.
+	and generate most of the _lasso_builtins.py file. When run, it creates a file
+	containing the types, traits, methods, and members of the currently-installed
+	version of Lasso 9.
 
 	A list of tags in Lasso 8 can be generated with this code:
 
@@ -29,14 +29,14 @@
 */
 
 output("This output statement is required for a complete list of methods.")
-local(f) = file("lassobuiltins-9.py")
+local(f) = file("_lasso_builtins-9.py")
 #f->doWithClose => {
 
-#f->openWrite
+#f->openTruncate
 #f->writeString('# -*- coding: utf-8 -*-
 """
-    pygments.lexers._lassobuiltins
-    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+    pygments.lexers._lasso_builtins
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
     Built-in Lasso types, traits, methods, and members.
 
@@ -46,18 +46,19 @@ local(f) = file("lassobuiltins-9.py")
 
 ')
 
-lcapi_loadModules
+// Load and register contents of $LASSO9_MASTER_HOME/LassoModules/
+database_initialize
 
 // Load all of the libraries from builtins and lassoserver
 // This forces all possible available types and methods to be registered
 local(srcs =
-	tie(
-		dir(sys_masterHomePath + 'LassoLibraries/builtins/')->eachFilePath,
-		dir(sys_masterHomePath + 'LassoLibraries/lassoserver/')->eachFilePath
+	(:
+		dir(sys_masterHomePath + '/LassoLibraries/builtins/')->eachFilePath,
+		dir(sys_masterHomePath + '/LassoLibraries/lassoserver/')->eachFilePath
 	)
 )
 
-with topLevelDir in #srcs
+with topLevelDir in delve(#srcs)
 where not #topLevelDir->lastComponent->beginsWith('.')
 do protect => {
 	handle_error => {
@@ -67,38 +68,53 @@ do protect => {
 	stdoutnl('Loaded: ' + #topLevelDir)
 }
 
+email_initialize
+log_initialize
+session_initialize
+
 local(
-	typesList = list(),
-	traitsList = list(),
-	unboundMethodsList = list(),
-	memberMethodsList = list()
+	typesList = set(),
+	traitsList = set(),
+	unboundMethodsList = set(),
+	memberMethodsList = set()
 )
 
 // types
 with type in sys_listTypes
-where #typesList !>> #type
+where not #type->asString->endsWith('$')		// skip threads
 do {
 	#typesList->insert(#type)
-	with method in #type->getType->listMethods
-	let name = #method->methodName
-	where not #name->asString->endsWith('=')		// skip setter methods
-	where #name->asString->isAlpha(1)		// skip unpublished methods
-	where #memberMethodsList !>> #name
-	do #memberMethodsList->insert(#name)
 }
 
 // traits
 with trait in sys_listTraits
 where not #trait->asString->beginsWith('$')		// skip combined traits
-where #traitsList !>> #trait
 do {
 	#traitsList->insert(#trait)
-	with method in tie(#trait->getType->provides, #trait->getType->requires)
+}
+
+// member methods
+with type in #typesList
+do {
+	with method in #type->getType->listMethods
+	where #method->typeName == #type	 // skip inherited methods
+	let name = #method->methodName
+	where not #name->asString->endsWith('=')		// skip setter methods
+	where #name->asString->isAlpha(1)		// skip unpublished methods
+	do {
+		#memberMethodsList->insert(#name)
+	}
+}
+with trait in #traitsList
+do {
+	with method in #trait->getType->provides
+	where #method->typeName == #trait		// skip inherited methods
 	let name = #method->methodName
 	where not #name->asString->endsWith('=')		// skip setter methods
 	where #name->asString->isAlpha(1)		// skip unpublished methods
-	where #memberMethodsList !>> #name
-	do #memberMethodsList->insert(#name)
+	do {
+		#memberMethodsList->insert(#name)
+	}
 }
 
 // unbound methods
@@ -108,36 +124,38 @@ where not #name->asString->endsWith('=')		// skip setter methods
 where #name->asString->isAlpha(1)		// skip unpublished methods
 where #typesList !>> #name
 where #traitsList !>> #name
-where #unboundMethodsList !>> #name
-do #unboundMethodsList->insert(#name)
-
-#f->writeString("BUILTINS = {
-    'Types': [
-")
-with t in #typesList
-do !#t->asString->endsWith('$') ? #f->writeString("        '"+string_lowercase(#t->asString)+"',\n")
-
-#f->writeString("    ],
-    'Traits': [
-")
-with t in #traitsList
-do #f->writeString("        '"+string_lowercase(#t->asString)+"',\n")
-
-#f->writeString("    ],
-    'Unbound Methods': [
-")
-with t in #unboundMethodsList
-do #f->writeString("        '"+string_lowercase(#t->asString)+"',\n")
+do {
+	#unboundMethodsList->insert(#name)
+}
 
-#f->writeString("    ]
+// write to file
+with i in (:
+	pair(#typesList, "BUILTINS = {
+    'Types': (
+"),
+	pair(#traitsList, "    ),
+    'Traits': (
+"),
+	pair(#unboundMethodsList, "    ),
+    'Unbound Methods': (
+"),
+	pair(#memberMethodsList, "    )
 }
 MEMBERS = {
-    'Member Methods': [
+    'Member Methods': (
 ")
-with t in #memberMethodsList
-do #f->writeString("        '"+string_lowercase(#t->asString)+"',\n")
+)
+do {
+	#f->writeString(#i->second)
+	with t in (#i->first)
+	let ts = #t->asString
+	order by #ts
+	do {
+		#f->writeString("        '"+#ts->lowercase&asString+"',\n")
+	}
+}
 
-#f->writeString("    ]
+#f->writeString("    )
 }
 ")