[Module-build-checkins] Module-Build/website dEx.pod,1.1,1.2

[Ken W. <kwi...@us...>]

Update of /cvsroot/module-build/Module-Build/website
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27000

Modified Files:
	dEx.pod 
Log Message:
minor edits to the POD and typo-fixing

Index: dEx.pod
===================================================================
RCS file: /cvsroot/module-build/Module-Build/website/dEx.pod,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** dEx.pod	9 Nov 2004 20:52:41 -0000	1.1
--- dEx.pod	9 Nov 2004 22:39:23 -0000	1.2
***************
*** 29,33 ****
  is considered true.
  
! In addition to returning true or false. Evaluation produces detailed
  information about what conditions were satisfied and, more
  importantly, which ones were not.
--- 29,33 ----
  is considered true.
  
! In addition to returning true or false, evaluation produces detailed
  information about what conditions were satisfied and, more
  importantly, which ones were not.
***************
*** 49,53 ****
  Checking for the presence of a module (any version).
  
! The simplest expresion is one that simply checks for the presence of a
  module, regardless of version:
  
--- 49,53 ----
  Checking for the presence of a module (any version).
  
! The simplest expression is one that simply checks for the presence of a
  module, regardless of version:
  
***************
*** 117,121 ****
  Checking for features
  
! Some modules provide optional features that may or may not be present
  or enabled. You can check for the presence of features:
  
--- 117,121 ----
  Checking for features
  
! Some modules provide optional 'features' that may or may not be present
  or enabled. You can check for the presence of features:
  
***************
*** 124,128 ****
  Features are specified by following a module name with a hash and one
  or more feature names in parenthesis separated by the logical and
! operator C<&&>. [???allow all logical operators???]
  
  [Does it make sense to allow something like:
--- 124,131 ----
  Features are specified by following a module name with a hash and one
  or more feature names in parenthesis separated by the logical and
! operator C<&&>.  Each feature will be checked by using the 
! C<< ...::ConfigData->feature($name) >> method, as described in the
! documentation for C<Module::Build>.  [???allow all logical
! operators???]
  
  [Does it make sense to allow something like:
***************
*** 163,169 ****
  =over 4
  
! =item *
! 
! B<{OSNAME}>
  
  Evaluates to a string containing the name of the current operating
--- 166,170 ----
  =over 4
  
! =item B<{OSNAME}>
  
  Evaluates to a string containing the name of the current operating
***************
*** 178,184 ****
    {OSNAME} in ['Linux' 'BSD' 'MacOSX']
  
! =item *
! 
! B<{ITHREADS}>
  
  Evaluates to true if ithreads are enabled.
--- 179,183 ----
    {OSNAME} in ['Linux' 'BSD' 'MacOSX']
  
! =item B<{ITHREADS}>
  
  Evaluates to true if ithreads are enabled.
***************
*** 190,196 ****
  =over 4
  
! =item *
! 
! B<HAS_INCLUDE()>
  
  Takes a list of one or more strings that are the names of include
--- 189,193 ----
  =over 4
  
! =item B<HAS_INCLUDE()>
  
  Takes a list of one or more strings that are the names of include
***************
*** 198,204 ****
  the include path.
  
! =item *
! 
! B<HAS_LIB()>
  
  Takes a list of one or more strings that are the names of libraries,
--- 195,199 ----
  the include path.
  
! =item B<HAS_LIB()>
  
  Takes a list of one or more strings that are the names of libraries,
***************
*** 206,212 ****
  library path.
  
! =item *
! 
! B<HAS_PROGRAM()>
  
  Takes a list of one or more strings that are the names of programs,
--- 201,205 ----
  library path.
  
! =item B<HAS_PROGRAM()>
  
  Takes a list of one or more strings that are the names of programs,
***************
*** 241,245 ****
  =head2 Making Choices
  
! Sometimes it's desirable to allow the use to specify constraints on
  certain expressions. For example, the {dbd} macro we used above:
  
--- 234,238 ----
  =head2 Making Choices
  
! Sometimes it's desirable to allow the user to specify constraints on
  certain expressions. For example, the {dbd} macro we used above:
  
***************
*** 290,316 ****
  =over
  
! =item *
! 
! Package Name
! 
! =item *
! 
! Version
! 
! =item *
! 
! Range
! 
! =item *
  
! String
  
! =item *
  
! Set
  
! =item *
  
! Tag
  
  =back
--- 283,297 ----
  =over
  
! =item Package Name
  
! =item Version
  
! =item Range
  
! =item String
  
! =item Set
  
! =item Tag
  
  =back
***************
*** 320,346 ****
  =over
  
! =item *
! 
! Relational operators
! 
! =item *
! 
! Equality operators
! 
! =item *
! 
! Set operator
! 
! =item *
  
! Tag operator
  
! =item *
  
! Logical operators
  
! =item *
  
! Assignment operator
  
  =back
--- 301,315 ----
  =over
  
! =item Relational operators
  
! =item Equality operators
  
! =item Set operator
  
! =item Tag operator
  
! =item Logical operators
  
! =item Assignment operator
  
  =back