Changes between Version 125 and Version 126 of ippToPsps

Timestamp:

Mar 11, 2011, 12:27:08 PM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -52 +52 @@
 == Design ==
 
-Each batch type (detection, stack, init etc) is it's own class, all of which inherit from the Batch base-class, which handles features common to all batches, such as creating and opening output FITS files, connecting to the GPC1 database, connecting with the DVO database etc. This keeps duplicated code at a minimum. The Batch is an abstract class, i.e. it should not, and cannot, be instantiated.
+Each batch type (detection, stack, init etc) is its own class, all of which inherit from the Batch base-class, which handles features common to all batches, such as creating and opening output FITS files, connecting to the GPC1 database, connecting with the DVO database etc. This keeps duplicated code at a minimum. The Batch class is an abstract class, i.e. it should not, and cannot, be instantiated.
 
 Each class has a single header file and a single source file. Public fields and methods are visible in the class (struct) definition in the header. Private members and functions are declared as static in the associated source files, thus keeping them encapsulated. All class code is contained in a single C file. Methods are accessed via function pointers in the structure.