Package lepl :: Package matchers
[hide private]
[frames] | no frames]

Source Code for Package lepl.matchers

 2  # The contents of this file are subject to the Mozilla Public License 
 3  # (MPL) Version 1.1 (the "License"); you may not use this file except 
 4  # in compliance with the License. You may obtain a copy of the License 
 5  # at 
 6  # 
 7  # Software distributed under the License is distributed on an "AS IS" 
 8  # basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See 
 9  # the License for the specific language governing rights and 
10  # limitations under the License. 
11  # 
12  # The Original Code is LEPL ( 
13  # The Initial Developer of the Original Code is Andrew Cooke. 
14  # Portions created by the Initial Developer are Copyright (C) 2009-2010 
15  # Andrew Cooke ( All Rights Reserved. 
16  # 
17  # Alternatively, the contents of this file may be used under the terms 
18  # of the LGPL license (the GNU Lesser General Public License, 
19  #, in which case the provisions 
20  # of the LGPL License are applicable instead of those above. 
21  # 
22  # If you wish to allow use of your version of this file only under the 
23  # terms of the LGPL License and not to allow others to use your version 
24  # of this file under the MPL, indicate your decision by deleting the 
25  # provisions above and replace them with the notice and other provisions 
26  # required by the LGPL License.  If you do not delete the provisions 
27  # above, a recipient may use your version of this file under either the 
28  # MPL or the LGPL License. 
30  ''' 
31  Matchers form the basis of the library; they are used to define the grammar 
32  and do the work of parsing the input. 
34  A matcher is like a parser combinator - it takes a stream, matches content in 
35  the stream, and returns a list of tokens and a new stream.  However, matchers 
36  are also coroutines that can be "recalled" to return alternative matches. 
37  This gives backtracking. 
39  Matchers are defined and implemented as both classes and functions.  I have  
40  used the same syntax (capitalized names) for both to keep the API uniform. 
42  For more background, please see the `manual <../index.html>`_. 
43  '''