[Openinteract-commits] CVS: SPOPS SPOPS.pm,1.48,1.49

[Chris W. <la...@us...>]

Update of /cvsroot/openinteract/SPOPS
In directory usw-pr-cvs1:/tmp/cvs-serv8815

Modified Files:
	SPOPS.pm 
Log Message:
lots of cosmetic changes (extra spaces, moving L<blah> to L<blah|blah> format, ...)


Index: SPOPS.pm
===================================================================
RCS file: /cvsroot/openinteract/SPOPS/SPOPS.pm,v
retrieving revision 1.48
retrieving revision 1.49
diff -C2 -d -r1.48 -r1.49
*** SPOPS.pm	2001/10/02 22:01:30	1.48
--- SPOPS.pm	2001/10/11 13:09:26	1.49
***************
*** 734,740 ****
  
  The individual objects or the classes should not care how the objects
! are being stored, they should just know that when they call I<fetch()>
  with a unique ID that the object magically appears. Similarly, all the
! object should know is that it calls I<save()> on itself and can
  reappear at any later date with the proper invocation.
  
--- 734,740 ----
  
  The individual objects or the classes should not care how the objects
! are being stored, they should just know that when they call C<fetch()>
  with a unique ID that the object magically appears. Similarly, all the
! object should know is that it calls C<save()> on itself and can
  reappear at any later date with the proper invocation.
  
***************
*** 778,782 ****
  This method creates a new SPOPS object. If you pass it key/value
  pairs the object will initialize itself with the data (see
! I<initialize()> for notes on this).
  
  Note that you can use the key 'id' to substitute for the actual
--- 778,782 ----
  This method creates a new SPOPS object. If you pass it key/value
  pairs the object will initialize itself with the data (see
! C<initialize()> for notes on this).
  
  Note that you can use the key 'id' to substitute for the actual
***************
*** 1256,1260 ****
  
  And be sure to include this class in your 'code_class' configuration
! key. (See L<SPOPS::Configure|SPOPS::Configure> for more info.)
  
  B<as_string>
--- 1256,1262 ----
  
  And be sure to include this class in your 'code_class' configuration
! key. (See L<SPOPS::ClassFactory|SPOPS::ClassFactory> and
! L<SPOPS::Manual::CodeGeneration|SPOPS::Manual::CodeGeneration> for
! more info.)
  
  B<as_string>
***************
*** 1325,1329 ****
  =head2 Configuration
  
! Most of this information can be accessed through the I<CONFIG>
  hashref, but we also need to create some hooks for subclasses to
  override if they wish. For instance, language-specific objects may
--- 1327,1331 ----
  =head2 Configuration
  
! Most of this information can be accessed through the C<CONFIG>
  hashref, but we also need to create some hooks for subclasses to
  override if they wish. For instance, language-specific objects may
***************
*** 1404,1417 ****
  =head1 NOTES
  
! There is an issue using these modules with I<Apache::StatINC> along
! with the startup methodology that calls the I<class_initialize> method
! of each class when a httpd child is first initialized. If you modify a
! module without stopping the webserver, the configuration variable in
! the class will not be initialized and you will inevitably get errors.
  
  We might be able to get around this by having most of the
  configuration information as static class lexicals. But anything that
  depends on any information from the CONFIG variable in request (which
! is generally passed into the I<class_initialize> call for each SPOPS
  implementation) will get hosed.
  
--- 1406,1420 ----
  =head1 NOTES
  
! There is an issue using these modules with
! L<Apache::StatINC|Apache::StatINC> along with the startup methodology
! that calls the C<class_initialize> method of each class when a httpd
! child is first initialized. If you modify a module without stopping
! the webserver, the configuration variable in the class will not be
! initialized and you will inevitably get errors.
  
  We might be able to get around this by having most of the
  configuration information as static class lexicals. But anything that
  depends on any information from the CONFIG variable in request (which
! is generally passed into the C<class_initialize> call for each SPOPS
  implementation) will get hosed.