What's fixed

What's fixed in OmniMark 6.5

• The reconnect sub-function of external output functions is now being called when the output stream is reopened.
• Quoted variable names were being allowed in some contexts. They are now prohibited in all contexts.
• ++ expressions with one or more pattern variables in the terminate pattern no longer cause an internal error.
• The date operator no longer outputs occasional spurious characters when using the am/pm indicator (=a or =A) in the format string.
• An internal error relating to saving global variables that are being used as modifiable function arguments has been fixed.
• Throwing using local variables as the read-only arguments of the throw, and then catching that throw outside the scope of the local variables no longer causes OmniMark to crash.
• Some errors and instabilities in the omldap library have been repaired
• The omsysout library now throws the correct exception when failing to start a program on UNIX.
• The ommail library no longer inserts null characters in lines longer than 512 bytes.
• In the omvfs library , these errors have been corrected:
  • vfsDescribe no longer fails on Windows when the target is on a read-only filesystem (such as a CD-ROM)
  • vfsDescribe now properly handles daylight savings time.
  • vfsMakeDir no longer ignores the user's umask on UNIX, and no longer sets more restrictive permissions than requested.
• In the omtcp library, clients connecting and disconnecting quickly will no longer cause a crash or an infinite loop.
• In the ombcd library, in one rare failure case, a crash would occur on some platforms while ombcd tried to throw an exception. This has been repaired.
• In the omfloat library, theses errors have been fixed:
  • The definition of round has been fixed to use "nearest" instead of "by"
  • round now handles half-way cases properly (e.g. 3.5 -> 4)
  • ceil, trunc and floor have been fixed to handle exceptional cases.
  • The outputting of NaN is now platform-independent
  • The outputting of scientific format floats is now platform-independent.

Fixed in OmniMark Studio 6.5

• When OmniMark Studio automatically loads a file during a debugging session, the include paths are now correctly used.
• An infrequently occurring buffer reading error has been fixed. This would happen while Studio was reading data from an edit window during a debugging session.
• Block operations are now enabled and disabled correctly according to whether or not the active edit buffer is writeable.
• In some situations, a pattern variable would appear twice in the local variables table. This no longer happens.
• Studio now permits debugging runs on the day its authorization is set to expire.

What's fixed in OmniMark 6.1.3b

Desktop Engine and Server Engine on the Windows platforms again correctly handle reading standard input from the command line. This fixes an error introduced in 6.1.3a.

The external function tcp-accept-connection (or TCPServiceAcceptConnection) no longer crashes OmniMark or sends it into an infinite loop if the connection is broken before the function returns.

What's fixed in OmniMark 6.1.3a

• Desktop Engine and Server Engine on the Windows platforms now correctly handle reading from standard input, when running as a CGI under IIS5.

What's fixed in OmniMark 6.1.3

• The file...is writable test works correctly for non-existant files in a writable directory.
• vfsLock no longer causes a file to be unreadable by the process using the vfsLock function.
• Rethrow from value-returning functions is now accepted by the compiler.
• always blocks now execute after uncaught external exceptions.
• The date operator now returns the correct timezone on Windows.
• An intermittent internal error, that has been present since 6.0, caused by an uninitialized variable, has been fixed.

What's fixed in OmniMark Studio 6.1.3

• OmniMark Studio now correctly identifies carriage returns as valid line-end markers.
• The Find/Replace dialog box is now correctly initialized when invoked without text selected in the active edit buffer.
• A markup parse with a parsing datascope visible no longer causes a memory violation when the parse terminates.
• The variables tables now correctly handle the case of optional, non-integer shelves in function calls, which previously caused off-by -one errors in their display.
• Exiting OmniMark Studio while running a program now displays a warning that the debugging session will be terminated, and offers the user a chance to cancel the operation.
• Whitespace characters are now handled correctly when copying text out of the log window, the shelf details window or the referent details window.
• The syntax colorization algorithm now correctly handles the case of a string-end marker preceded by multiple escape characters. For instance, the string "%%%" is now colored as an unterminated string.
• OmniMark Studio now properly frees dynamic library resources between runs.

What's fixed in OmniMark 6.1.2

The following problems have been fixed in version 6.1.2

• A memory leak relating to the use of dynamically-formed keys for shelves was closed. Now you can create shelves dynamically without leaking memory, either by issuing code such as
  

    new my-shelf {"d" % i}
  

  or by issuing
  

    set new my-shelf {"d" %i} to "fred"
  

• There is no longer a duplicate error message produced when throws generated by external functions are not caught by the calling program.

What's fixed in OmniMark 6.1.1

• Using dynamically-formed keys for shelves no longer causes a memory leak (a defect introduced in 6.0.2).
• In the omoci library (Oracle Call Interface database support), database and cursor handles are now closed correctly. They were not being closed until the end of the OmniMark run, causing some programs to run out of handles.

What's fixed in OmniMark Studio 6.1.1

Studio once again reads large program and data files correctly. A defect introduced in version 6.1 caused Studio to occasionally read large programs and data files incorrectly when they were loaded into edit buffers.

What's fixed in OmniMark 6.1

The following problems have been fixed in version 6.1

• When using rethrow, rethrowing an external-exception will now be consistent with rethrows of all other types of exceptions.
• In user-written external function libraries, the entire OMX API is now available to the creator subfunction.
• The repeated operator (||*) now does proper range checking for negative numbers in all cases.
• An internal error related to empty patterns and pattern assignment while doing a repeat scan has been fixed.

What's fixed in OmniMark Studio 6.1

Problems have been fixed so that OmniMark Studio

• Displays data more rapidly in all datascopes (such as the Parsing Sources datascope and the Scanning Sources datascope)
• Processes all characters correctly, including those whose value is greater than 127. (Previously, if your OmniMark program accessed files that were open in an edit buffer and those files contained such characters, the results were unpredictable)

For further information, see the OmniMark Studio Windows help file.

What's fixed in OmniMark 6.0.2

The following problems have been fixed in version 6.0.2

• Element rules immediately preceded by catch declarations are now always being selected during an XML parse.
• integer and counter are useable interchangeably as casting operators for user-defined conversions function casts.
• Casting user-defined OMX types using converstion-functions no longer result in internal error 1039-115.
• using #group will now save the group set for restoration.
• When doing #current-input matches... certain patterns will not cause characters to be consumed from #current-input even when the matches failed.
• Error checking in the library omtcp-old (a deprecated TCP/IP client and server support library) interface has been cleaned up.
• OmniMark external function API which adds support for making external function libraries thread-safe has been updated.
• OmniMark error messages have been enhanced for when unable to bind an external function or load an external function library.

What's fixed in OmniMark 6.0.1

The following problems have been fixed in version 6.0.1

core language

• -stats now gives timing statistics again.
• Earlier versions erroneously allowed some functions and variables to share a name. Such name sharing will now trigger an error.
• Release subfunctions that trigger external exceptions were getting invoked a second time. This behavior has been corrected.
• Characters that fell through during a submit were enabling empty patterns to fire twice consecutively rather than once only.
• Problems with internal errors and corrupted values for complex dynamic initializers have been fixed.
• An internal error with occurrence count ranges used on a string constant has been fixed.
• An internal error triggered by "++=>" being used in a take expression has been fixed.
• Key based default item indexing didn't detect the disappearance of the default item key, and so allowed access to a default item that should no longer have been accessible. This behavior has been corrected.
• Strings being converted to numbers at run time were producing wrong values when the strings contained "_" characters. This behavior has been corrected.
• Numeric literals were erroneously being accepted wherever stream values were expected. Such a condition will now trigger an error.

omvfs library

• The function vfsMove now works across devices on UNIX platforms.
• Microsoft Windows drive letters now work with omvfs functions.

omdb library

• Case sensitivity of table fields has been removed.
• The function dbProcedureExecute now checks for the presence of a result set, and dbProcedureOpen does not.
• Before dbRecordMove is executed, it will check whether the dbField argument shelf is empty, and whether it's positioned on a valid row,
• The trailing zeros in the numeric fields that were returned by Oracle have been removed.

What's fixed in OmniMark 6.0

• The following problems have been fixed in version 6.0. This list includes fixes to problems discovered in public betas of OmniMark 6:
• The copy-clear produced a run-time error when used on a modifiable shelf function argument.
• The null pattern modifier did not work correctly with repeat scan.
• The ++ and ** occurrence indicators were causing the ul pattern modifier to extend beyond its proper scope.
• using input as was not behaving correctly inside a match body of a do scan #current-input.
• Cascading numeric comparisons of strings and numbers (for example 1 < "2" < 98 were causing an internal error.
• do when with a catch block was erroneously falling through from the catch block to the else clause.
• Consecutive occurrence indicators that should have been flagged as an error were being allowed.
• The expression name of #main-output was causing a syntax error.
• In rare circumstances, patterns would sometimes fail to match.
• Full string expression syntax was not supported inside curly brace indexers.
• If a new shelf action failed because of key collision, an unspecified shelf item was incorrectly created.
• Sub-pattern variable assignment in a pattern which failed caused an internal error.
• Pattern variable assignment in a repeatedly executed null find rule caused an internal error.
• Repeated use of the pcdata character type in a pattern failed to match correctly.
• Positional patterns were incorrectly restricted from occurring in patterns. As a consequence of this correction, positional patterns are now allowed in more pattern-matching contexts.
• Outer pattern variables became corrupted in nested #current-input scans.
• In some cases, an uncaught #external-exception did not result in a throw to #program-error.
• The ul pattern operator scope was incorrectly extended to the end of the pattern.
• Throws from the sub-functions of OMXs, external sources, and external output objects failed.
• The matching position of #current-input was incorrectly restored when exiting or throwing out of a repeat scan.
• The ommail library has had an error that duplicated periods that occurred in the mail message.
• Variable type-heralds are no longer allowed. They were allowed in some places; this was an error. Some programs may need fixing when ported to this version of OmniMark. This error was introduced with OmniMark 5.3.
• An interaction among #current-input, submit, and pattern variables was causing incorrect behavior.
• The pattern word-end was being handled incorrectly. This was introduced with OmniMark 5.3.
• Functions that contain only catch blocks were being handled incorrectly. This error was introduced with OmniMark 5.3.
• The test
  

       do when <string-expression> matches ...
  

  was not supported. This error was introduced with OmniMark 5.3.
• Start-tags containing more than 180 element attributes were causing a memory allocation error.
• An interaction between reopen, keys, filenames, and function-calls was causing incorrect behavior.

----

[ INDEX ] [ CONCEPTS ] [ TASKS ] [ SYNTAX ] [ LIBRARIES ] [ OMX ] [ ERRORS ]