Waiting for Gauthier feedback (2).

diff --git a/src/ParaMEDMEM/DisjointDEC.cxx b/src/ParaMEDMEM/DisjointDEC.cxx
index 1b1c2f360b16e1ff213f9a2bc7978507adf06ed0..df83ad736320327e33d63019c6b8f3f27410a2dd 100644 (file)
--- a/src/ParaMEDMEM/DisjointDEC.cxx
+++ b/src/ParaMEDMEM/DisjointDEC.cxx
@@ -42,8 +42,7 @@
  * On top of attaching a \c ParaMEDMEM::FIELD, it is possible to
  * attach a ICoCo::Field. This class is an abstract class that enables 
  * coupling of codes that respect the ICoCo interface \ref icoco. It has two implementations:
- * one for codes that express their fields as \ref medoupling fields (ICoCo::MEDField) and one
- * for codes that express their fields as Trio/U fields.
+ * one for codes that express their fields as \ref medoupling fields (ICoCo::MEDField).
  * 
  * \section dec_options DEC Options
  * Options supported by \c DEC objects are
@@ -254,7 +253,6 @@ namespace ParaMEDMEM
     Reversely, if the processor is on the sending end, the field will be read, possibly transformed, and sent appropriately to the other side.
     The field type is a generic ICoCo Field, so that the DEC can couple a number of different fields :
     - a ICoCo::MEDField, that is created from a MEDCoupling structure
-    - a ICOCo::TrioField, that is created from tables extracted from a TRIO-U structure.
     
   */
   void DisjointDEC::attachLocalField(const ICoCo::MEDField *field)

diff --git a/src/ParaMEDMEM/ICoCoMEDField.hxx b/src/ParaMEDMEM/ICoCoMEDField.hxx
index 95b873a539a2e5e177b5ea2acc173699f8275567..30a65005a7c5d57505cc93facf876458f9af94c9 100644 (file)
--- a/src/ParaMEDMEM/ICoCoMEDField.hxx
+++ b/src/ParaMEDMEM/ICoCoMEDField.hxx
@@ -28,8 +28,6 @@
 
 namespace ICoCo
 {
-  class TrioField;
-  
   class MEDField : public ICoCo::Field
   {
   public: