To reach this target, we have to face two problems:
- %A naming conflict with the instruction <b>import salome</b>. The result
- is unpredictible because of the existence in the <b>sys.path</b> of
+ is unpredictable because of the existence in the <b>sys.path</b> of
both a file <b>salome.py</b> and a package \b salome.
- The dispatching of <b>salome.*</b> sub-packages in the different %SALOME
modules.
*
* Note that neither ptrPoint, nor ptrDestruct should be destroyed by the user.
*
- * The destruction object must be created dynamically because it suscribes
+ * The destruction object must be created dynamically because it subscribes
* itself in the list of destruction to be performed at the end of the process.
*/
// ============================================================================
// << _StartUsed << std::endl ;
}
#else
- // NOT implementet yet
+ // NOT implemented yet
#endif
}
//============================================================================
-/*! Function : Desctructor
+/*! Function : Destructor
* Purpose :
*/
//============================================================================