Fixed Problems

• Eloquence uses a fixed intermediate buffer for the DLG SET statement which is currently limited to 4K. This buffer should be allocated dynamically. (#453)

• The eloq program did not work with STREAMS (HP-UX 10.20, rlogin). In addition, eloq as distributed on media with datecode before 70903 had an internal problem which could result in a failure (break detected ...). A patch is available at ftp://ftp.marxmeier.com/eloq/A0600/patch). (#492)

Known Problems

• DBERASE / DBCREATE statement compatibility
  When using eloqdb6, the optional maintenace word is no longer used. You should use the DBLOGON statement to establish a user with sufficient capabilities.

• The dbtables utility does currently not report collating sequences and data set capacity.

• Cross reference (list -x) complains about user defined types
  The cross reference (list -x) currently has some problems dealing with user defined types (STRUCT). It is complaining about multiply declared or unused member variables. (#458)

• The TopItem attribute is currently not recognized by the DLGSRV as a mapped attribute. As a workaround, you could use TopItem as a native attribute. Just separate the attribute and object path with an exclamation mark instead of a dot. (#450)

  DLG SET "Dialog.ListBox!TopItem",3
  

• The .h attribute is currently ignored by DLGSRV for PushButton objects. As a workaround, you could use Height as a native attribute. Just separate the attribute and object path with an exclamation mark instead of a dot. (#463)

  DLG SET "Dialog.Pb_OK!Height",3
  

• Eloquence does not accept an implied LET using a structured type after a THEN. As a workaround, simply use explicit LET. (#392)

  IF Condition THEN LET Instance.Member=25
  

• The Eloquence syntax analyse results in a syntax error with the statement below:

  FOR I=1 TO A STEP C
  

  The problem is, that the keyword AS is recognized errorneously. As a workaround, simply use a different variable name or use an expression (eg. A+0). (#454)

• QFIND with IN clause on an index may return unexpected results if the collating sequence of the index and the program executing QFIND is different. QFIND internally uses DBFIND to position into the index and then retrieves data in index order until the max. value is exhausted. However the max. value is checked using collating sequence (this is required to handle national characters properly, eg. in German A umlaut needs to be inserted between A and B). If the max. value is greater (or less) than the first index value retrieved from the index, this will result in either an empty result or an unexpected number of result records. (#493).

Windows Platform

• Handling of constant values in the graphical devlopment environment. It has been reported that a constant value could change its representation from normal (181295) to exponentioal notation (1.81295E5) when the cursor touches the line. (#461)

• Some trace output could be lost when executing eloqcore locally. This is caused by Windows NT which simply discards any networking data when the eloqcore process ends and the IDE did not yet receive all trace information.

• Output of system commands is lost, when the command contains a pipe.
  This does at least happen with the mks shell.
  For example: COMMAND "!ls -l|grep Feb"

• QUERY and other utilitiy programs such as CFORM, MFORM and PFORM require character I/O which is not available on Windows NT. There are currently no plans to provide a graphical version of the QUERY program.

Linux Platform

• Frequent segment violation / core dumps on Linux

  You need to install compatible shared library versions on your Linux system (see Linux installation notes for more information).

• The Linux console does not support the underline display enhancement.

• The eloq program is not available on Linux. The eloq programs is used to provide virtual terminal capabilities (aka. TASKS) for Eloquence. This is done by using ptys (pseudo tty devices) to connect the eloqcore processes to eloq.
  However the method we use to communicate tty parameters and control information between eloq and eloqcore is not available in the Linux kernel. So eloq can currently not be ported to the Linux platform until we change the implementation. However, since Linux provides buitin virtual consoles and the X Windows System could be used with a terminal window this should not be a real problem.