
        PROBLEMS.TXT copyright(c) 1991-1993 xTech, RTA            page 1
        ----------------------------------------------------------------

                                    Oberon-2
                                    --------

        There should be no problems with Extacy Oberon-2 compiler. It is
        fully compliant with a latest (June 1993) ETH Oberon-2 standard.


                                    Modula-2
                                    --------

        There are a lot of Modula-2 dialects. Extacy  Modula-2  compiler
        is  almost  fully  PIM  4th  edition  and  ISO  WG13   standards
        compatible.

        Please see below a list of obsolete, non-standard, non-portable,
        not ISO WG13 and PIM compliant  constructions  Extacy  does  not
        support.

        - Non-standard compiler-dependent Modula-2  extensions  are  not
          supported. Almost all such extensions are superfluous and  can
          easily be expressed using standard ISO Modula-2.  Contact  RTA
          if you have any problems.

        - EXPORT and EXPORT QUALIFIED statements in  definition  modules
          are obsolete. Remove such declarations from definition modules

        - SYSTEM.SIZE is obsolete. Use standard procedure SIZE instead.

        - Type casting using TypeName(Expression)  is  obsolete.  Though
          Extacy supports it, it is better to  use  VAL  or  SYSTEM.CAST
          (TypeName,Expression) instead.

        - Extacy require to use "FORWARD" procedures  declarations  when
          necessary (ISO WG13 "declare-before-use" approach).

        - INTEGER and CARDINAL types and their variations are assignment
          compatible. No type conversion is required,  but  Extacy  will
          generate an appropriate run-time check.

        - Use standard procedures  LFLOAT  and  FLOAT  to  perform  type
          conversions to LONGREAL and REAL. {L}FLOAT(x) is equivalent to
          VAL({LONG}REAL, x).

        - Unlike some compilers Extacy  performs  strict  type  checking
          according to ISO WG13 proposals, that is:

                - FOR loop control  variable  is  read-only  (cannot  be
                  passed as VAR parameter, assigned a value, etc).

                - ARRAY [0..4] and ARRAY [1..5] are not compatible.






        ----------------------------------------------------------------
        PROBLEMS.TXT copyright(c) 1991-1993 xTech, RTA            page 1

        PROBLEMS.TXT copyright(c) 1991-1993 xTech, RTA            page 2
        ----------------------------------------------------------------

                                   Bug report
                                   ----------

        If you suspect you found a bug:

                1. Ensure you have a latest version of Extacy.

                2. Ensure ALL your sources had been  recompiled  by  the
                   latest version of Extacy.

                3. Ensure your sources ISO WG13 compliant.

                4. Ensure ALL your sources had been compiled with the  C
                   compiler with exactly the same flags.

                5. Ensure whenever possible it is not  your  C  compiler
                   error (however it is not necessary).

        If you are still sure it is Extacy bug, please report it to  us.
        We are grateful indeed for bug reports.

        You can make  our  life  easier  if  you  provide  us  with  the
        following information:

                - version number of Extacy you use

                - platform details (CPU, FPU, and operation system)

                - C compiler you use (including version number)

                - C compiler flags

                - Extacy compiler options

        complete with a minimal piece of source code causing error.


                                [end of document]


















        ----------------------------------------------------------------
        PROBLEMS.TXT copyright(c) 1991-1993 xTech, RTA            page 2

