jon         00/10/15 12:29:50

  Modified:    specification questions
  Log:
  added my comments to the questions.
  
  Revision  Changes    Path
  1.2       +20 -0     jakarta-velocity/specification/questions
  
  Index: questions
  ===================================================================
  RCS file: /home/cvs/jakarta-velocity/specification/questions,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- questions 2000/09/30 17:04:20     1.1
  +++ questions 2000/10/15 19:29:49     1.2
  @@ -18,6 +18,13 @@
      after the #foreach. The value of $element is
      not available after the #foreach block.
   
  +   <Jon S. Stevens>
  +   $element should not be available after the foreach
  +   There should be a $velocity_count variable available
  +   within the scope of the foreach. This variable should
  +   start value should be a preference in the velocity.properties
  +   file.
  +
   -------------------------------------------------------
   
   2. How should expressions in #if/#elseif be
  @@ -34,6 +41,11 @@
      If $variable is defined and is not a Boolean
      object then the expression is true.
   
  +   <Jon S. Stevens>
  +   I agree with the above. However, if $variable evaluates to 
  +   null, then the result should be false. If $variable is not a 
  +   Boolean and it is not null, then it should evaluate to true.
  +
   -------------------------------------------------------
   
   3. How are null values to be handled?
  @@ -51,6 +63,11 @@
      
      Or should it be configurable?
   
  +   Current Implementation:
  +   
  +   Right now, if it is null the image of the token is spit out:
  +   ie: $foo. But, if the token is $!foo then nothing is output.
  +
      Responses:
      
      <Daniel L. Rall>
  @@ -58,3 +75,6 @@
      implementation that logs the null (minimally!) and puts nothing in the
      output.
   
  +   <Jon S. Stevens>
  +   I agree with Daniel, except that I would add to the default implementation to 
  +   make it to spit it out as a literal.
  
  
  

Reply via email to