Qore Programming Language Reference Manual  0.9.14
Release Notes

Table of Contents

Qore 0.9.14

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • OracleSqlUtil module updates:
    • fixed a bug where pseudocolumn references were used ambiguously in joins (issue 4214)
    • fixed a bug where pseudocolumn names were quoted in queries leading to errors (issue 4210)
    • added an exception when offset or limit are used with forupdate (issue 4206)
  • SqlUtil module updates:
    • fixed a bug where pseudocolumn references were used ambiguously in joins (issue 4214)
  • Swagger module updates:
    • fixed a bug where unknown string format types were not ignored but instead caused an exception to be thrown (issue 4203)
  • Util module updates:
    • fixed a bug in parse_memory_size() with numbers larger than 9 (issue 4198)
  • fixed module path handling on Windows to respect the ';' separator as well as the ':' character (issue 4154)

Qore 0.9.13

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • Mapper module updates:
    • fixed a bug handling the struct key in mappers (issue 4189)

Qore 0.9.12

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • fixes in modules
  • fixed module path handling on Windows to respect the ';' separator (issue 4154)

Qore 0.9.11

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • CsvUtil
    • updated read and write data providers to provide verbose option support (issue 4139)
    • implemented support for the missing bool and *bool types (issue 4118)
  • DataProvider
    • fixed an issue where it was not possible for pipeline to flush any pending data or to perform reset or purge operations when pipeline processing is complete; for this the AbstractDataProcessor::flush() and AbstractDataProcessor::flushImpl() methods were implemented (issue 4107)
  • FixedLengthUtil
    • updated read and write data providers to provide verbose option support (issue 4139)
  • HttpServer
    • fixed a bug shutting down dedicated socket I/O handlers (issue 4130)
    • fixed a bug where invalid HTTP responses were send with error messages and chunked transfer encoding (issue 4124)
    • fixed a bug where HTTP stream handlers could not also implement protocol switching (issue 4111)
  • HttpServerUtil
    • fixed a bug where it was not possible to include CORS headers or any context-sensitive information in a 401 response (issue 4136)
    • fixed a bug where HTTP stream handlers could not also implement protocol switching (issue 4111)
    • fixed a bug handling responses to streaming requests with HEAD requests with a Transfer-Encoding: chunked response (issue 4109)
  • ServiceNowRestDataProvider
    • fixed a type error in DataProvider API support (issue 4104)
  • fixed support for 64-bitARM CPUs; added stack guard support (issue 3965)
  • fixed a bug handling types in assignments with complex hashes (issue 4133)
  • fixed a bug in the remove operator when used with a slice of a hash or an object; hash keys for nonexistent values were returned in a manner inconsistnent with the hash slice operator when not used with the remove operator (issue 4122)
  • fixed a bug in the cast<> operator; invalid exceptions were raised during parsing for values that could still inherit the target class; the check must only be made at runtime (issue 4113)
  • fixed a bug in the instanceof operator; invalid exceptions were raised during parsing for values that could still inherit the target class; the check must only be made at runtime (issue 4112)
  • fixed a bug where it was not possible to poll for I/O on more than one Socket at a time; for this the Socket::poll() static method was implemented (issue 4069)

Qore 0.9.10

Release Summary
Bugfix release; see below for more information

New Modules in Qore

Bug Fixes in Qore

  • WebUtil module updates:
    • fixed a bug serving files did not work in server contexts with multiple threads (issue 4096)
  • fixed an invalid assert in class handling in complex hierarchies (issue 4094)

Qore 0.9.9

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • RestClient module updates:
    • additional fixes to REST path handling with schema validators with a base path (issue 4059)

Qore 0.9.8

Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

Qore 0.9.7

Release Summary
Bugfix release; see below for more information

Release Notes

Note that when a REST validator is present in a REST connection, any URI path in the connection URL is ignored; to change the base path specified by a REST validator, use the swagger_base_path connection option.

Bug Fixes in Qore

  • DataProvider module updates:
    • fixed type-handling bugs handling data provider options (issue 4062)
  • RestClient module updates:
    • fixed a bug where the base path in the Swagger schema was ignored; note that when a REST validator is present, any URI path in the connection URL is ignored; to change the base path specified by a REST validator, use the swagger_base_path connection option (issue 4059)
  • Swagger module updates:
    • fixed a type error in Swagger::getBasePath() for the case when the base path is not set (issue 4064)
  • WebSocketHandler module updates:
    • fixed a bug handling the case when a connection object is deleted in a callback method (issue 4063)

Qore 0.9.6

Note
From Qore 0.9.6 onwards, Qore releases will use semantic versioning.
Release Summary
Bugfix release; see below for more information

Bug Fixes in Qore

  • DataProvider module updates:
    • fixed invalid default return values for AbstractDataProcessor methods (issue 4043)
  • RestClient module updates:
    • added the swagger_base_path option to REST clients and connections to allow for Swagger schemas to have their base path overridden (issue 4059)
  • SwaggerDataProvider module updates:
    • fixed a bug where the base path in the Swagger schema was ignored (issue 4059)
  • fixed a problem with lazy resolution of static class variables that could lead to incorrect runtime execution (issue 4045)
  • fixed a symbol conflict with the gettid() C++ function; use q_gettid() instead to avoid potential symbol conflicts that can result in a crash (issue 4046)
  • fixed a bug handling the class context in closures created with the background operator when created in the context of a subclass of the method called (issue 4051)
  • fixed a bug that could cause a crash destroying thread-local vars when threads terminate (issue 4053)
  • fixed a race condition that could cause a crash when deleting closure-local variable data while holding a lock (issue 4055)

Qore 0.9.5

Release Summary
Bugfix release with minor new features; including full ARM CPU support; see below for more information

Fixes That Can Affect Backwards-Compatibility

  • The ConnectionProvider module was updated with support for verbose option reporting and a connection cache; support for the deprecated constructor was removed from HttpConnection, HttpBasedConnection, as well as from other connection classes
  • The mkdir() function was modified to provide consistent behavior and a consistent return value with and without the parents argument; this function never throws an exception now, and always returns either 0 (meaning no error occurred) or 1 (meaning an error occurred) and no longer returns the number of directories created when parents = True. Use Dir::create() to get the number of directories created as in previous versions of Qore;
    See also
    Qore::mkdir_ex()
  • Fixed broken range() and xrange() where the upper limit of the range was included in the result for maximum compatibility with other languages. To get the old behavior, use the %broken-range parse directive.
  • Floating-point values are always converted to strings with a decimal point; in previous releases of Qore, round floating-point values were converted to strings without any decimal point; i.e. 1.0 will now be converted to "1.0" (in previous releases of Qore, it would be converted to simply "1")

New Features in Qore

  • CdsRestClient
    • new module providing APIs for communicating with the Microsoft Common Data Service REST API
  • CdsRestDataProvider
    • new module providing a data provider API for the Microsoft Common Data Service REST API
  • ConnectionProvider
    • added support for verbose connection option reporting
    • added a connection cache
    • all connection classes updated to support verbose option reporting
  • DataProvider module updates:
    • added new Qore base types to the data type hierarchy
    • implemented the following classes:
      • AbstractDataProcessor
      • DataProviderBulkRecordIterator
      • DataProviderPipeline
        (issue 3876)
    • added the DUPLICATE-RECORD exception documentation for AbstractDataProvider::createRecord()
    • updated to allow data provider type attributes to appear as children in the type hierarchy (issue 4015)
  • FsUtil module updates:
  • reflection module updates:
    • added AbstractConstant::getModuleName()
    • added AbstractReflectionFunction::getCodeFlags()
    • added AbstractReflectionFunction::getCodeFlagList()
    • added AbstractReflectionFunction::getDomain()
    • added AbstractReflectionFunction::getDomainStringList()
    • added AbstractReflectionFunction::getModuleName()
    • added Namespace::getModuleName()
    • added TypedHash::doCast()
  • RestClient
    • added the no_charset option to options (issue 3328)
  • RestSchemaValidator
    • added the no_charset option to options (issue 3328)
  • Schema module updates:
    • allow schema operations to be executed with no output (verbose < 0) (issue 3996)
  • SqlUtil module updates:
    • new AbstractTable methods returning a hash with info about the operation as well as the SQL and any bind arguments used
  • Util module updates:
    • added the parse_memory_size() function (issue 4004)
  • New data type:
  • New methods:
  • New functions:
  • Added stack guard support for ARM processors (issue 3965)

Bug Fixes in Qore

  • DataProvider module updates:
    • fixed a bug where HashDataType would not enforce fields or field types when checking for type and value compatibility (issue 4037)
  • FreetdsSqlUtil module updates:
    • fixed a bug generating literal date/time values for SQL queries (issue 3948)
  • HttpServer module updates:
    • fixed a bug where the HTTP server would not always stop the ThreadPool which caused process shutdowns to hang (issue 3999)
    • fixed a bug where the Expect header was not supported and where binary message bodies were read as strings (issue 4035)
  • MysqlSqlUtil module updates:
    • fixed a bug generating literal date/time values for SQL queries (issue 3948)
  • PgsqlSqlUtil module updates:
    • implemented atomic merge / upsert support (issue 3963)
    • fixed a bug generating literal date/time values for SQL queries (issue 3948)
  • Qdx module updates:
    • fixed a bug where Qore-language post processing fixes were applied to non-Qore docs (issue 3985)
  • QUnit module updates:
    • updated to allow tests to be run with argument handling from languages that do not support lvalue references (issue 3934)
  • fixed a bug in range() and xrange() where the upper limit of the range was included in the result (issue 4031)
  • fixed a bug in exception handling with external language modules where stack trace elements were added in reverse order (issue 4030)
  • fixed a bug in Qore::mkdir() with parents = True (issue 3992)
  • fixed a bug where complex formatting output with sprintf() and related dunctions would have "." separators instead of "," separators when floating-point values were included in the output (issue 3947)
  • fixed a bug handling embedded nulls in UTF-8 strings (issue 2942)

Qore 0.9.4.7

Release Summary

Bugfix release; see details below

Bug Fixes in Qore

Qore 0.9.4.6

Release Summary

Bugfix release; see details below

Bug Fixes in Qore

Qore 0.9.4.5

Release Summary

Bugfix release; see details below

New Features in Qore

Bug Fixes in Qore

  • Mapper module updates:
    • fixed a bug handling external runtime keys with bulk input for keys that do not require the current input value (issue 3931)
  • fixed a race condition in closure-bound variable reference handling that could result in a runtime crash (issue 3939)

Qore 0.9.4.4

Release Summary

Bugfix release; see details below

New Features in Qore

  • Mapper module updates:
    • added support for mapper context in mapper field key handlers (issue 3893)
    • added support for nested mappers and the submappers option (issue 3414)
    • implemented the output_create_ignore_duplicates option
  • added support for freestanding expression evaluation:

Bug Fixes in Qore

  • CsvUtil module updates:
    • fixed FixedLengthWriteDataProvider to return the record created with the createRecord() call (issue 3914)
  • DataProvider module updates:
    • added the DUPLICATE-RECORD exception documentation for AbstractDataProvider::createRecord()
  • FixedLengthUtil module updates:
    • fixed CsvWriteDataProvider to return the record created with the createRecord() call (issue 3914)
  • Mapper module updates:
    • fixed a bug where mapper output data was not logged in case of an error in an output provider (issue 3909)
    • updated mapper key handler calling convertion + docs (issue 3894)
    • fixed Mapper::mapAuto() to return NOTHING with no input (issue 3872)
  • SalesforceRestDataProvider module updates:
    • fixed a bug deleting records with no matches (issue 3921)
    • fixed serializing DATE fields (issue 3908)
  • fixed a bug in class copy methods with private:internal members (issue 3901)
  • fixed bugs running qdbg (issue 3900)

Qore 0.9.4.3

Release Summary

Bugfix release; see details below

New Features in Qore

  • DataProvider module updates:
    • added new classes:
      • AbstractDataProcessor
      • DataProviderBulkRecordIterator
      • DataProviderPipeline
      (issue 3876)
  • Mapper module updates:
    • added the Mapper::mapAuto() method and the disable_bulk option (issue 3872)
    • Mapper now inherits DataProvider::AbstractDataProviderRecordProcessor (issue 3876)

Bug Fixes in Qore

  • fixed a bug in the ThreadPool class where queued tasks were discarded without being executed when ThreadPool::stopWait() was called (issue 3897)
  • fixed a bug determining method signature compatibility with variants of the softlist type (issue 3887)
  • fixed a parse-time type error taking a slice of a hashdecl value (issue 3882)
  • fixed HTTP responses with no message body and no Transfer-Encoding header to include a Content-Length: 0 header to correctly support RFC-2616 (issue 3879)
  • fixed a crash in handling reference arguments in call references in mixed class contexts (issue 3869)
  • fixed a memory leak in the code that manages remote client certificates in the Socket class (issue 3865)

Qore 0.9.4.2

Release Summary

Bugfix release; see details below

New Features in Qore

Bug Fixes in Qore

Qore 0.9.4.1

Release Summary

Bugfix release; see details below

New Features in Qore

  • New FileLocationHandler module: provides an API for retrieving file data based on a URL-like location string

Bug Fixes in Qore

  • DataProvider module:
    • allow type paths to resolved to internal fields in DataProvider::getType() and DataProvider::getTypeEx() (issue 3791)
  • Mapper module:
    • added the Mapper::setNullableOutput() method and the output_nullable option (issue 3788)
  • Swagger module:
    • added support for the x-nullable attribute to allow for nullable values (issue 3785)
    • fixed support for types with no type declaration (issue 3775)
  • SwaggerDataProvider module:
    • fixed support for requests that do not require a request hash (issue 3784)

Qore 0.9.4

Release Summary
The main new feature in this release is the DataProvider API, which provides a generic API for introspecting and manipulating data in any format and over any protocol. Qore 0.9.4 also contains many usability and consistency fixes as well.

Fixes That Can Affect Backwards-Compatibility

  • RestHandler module: renamed RestHandler::getPossibleSubClasses() to RestHandler::doGetPossibleSubClasses() in order to avoid a collision with a REST method name (issue 3614)
  • fixed broken cast<> operator handling; in previous releases, cast<> would accept and return NOTHING without raising an error with type specifications that did not accept or return NOTHING. To get the old behavior, use the %broken-cast parse directive.
  • disallowed the use of the deprecated returns keyword by default. To get the old behavior, use the %allow-returns parse directive.
  • classes inheriting AbstractConnection must be serializable; the AbstractConnection::getConstructorInfo() and AbstractConnection::getConstructorInfoImpl() methods have been removed and are ignored in child classes
  • the following are now reserved words in Qore to prohibit them from being redefined:

New Features in Qore

Bug Fixes in Qore

  • fixes in modules:
  • the default exception handler now shows the exception "arg" key exceptions in builtin code if present (issue 3768)
  • fixed reporting the exception location when exceptions occur in builtin code (issue 3742)
  • fixed type handling in list and hash evaluation with complex types that can only be determined at runtime (issue 3740)
  • fixed setting the time zone region in date/time values to not include the system-specific zoneinfo path prefix in order to allow for deserialization of date/time values on different systems (issue 3736)
  • fixed a crash in parse error handling for recursive constant parse hash resolution cases (issue 3708)
  • fixed a bug retrieving HTTP message bodies with servers that do not send a Content-Length header but close the connection (issue 3691)
  • fixed inconsistent handling of the += operator with *list<...> types with element types (issue 3586)
  • <string>::split(string, string, bool) and Qore::split(string, string, string, bool) now properly handle double quote characters as an alternative way to include quotes in fields (issue 3550)
  • the cast<> operator can now cast directly to "or nothing" types: ex:
    *list<int> l = cast<*list<int>>(getList());
    (issue 3331)
  • fixed detecting invalid input in date(string, string) (issue 3239)

Qore 0.9.3.3

Release Summary

Bugfix release; see details below

Bug Fixes in Qore

  • fixed a bug where a crash would result when calling Datasource::getOption() when the connection was closed (issue 3754)
  • MysqlSqlUtil module fix: updated to work also with newer versions of MySQL / MariaDB that support sequences (issue 3747)
  • fixed a bug where the Datasource class would not always remove the transaction thread resource when rolling back transactions (issue 3745)

Qore 0.9.3.2

Release Summary

Bugfix release; see details below

New Features in Qore

Bug Fixes in Qore

  • RestHandler: fixed a bug handling exceptions in REST methods with unserializable exception data (issue 3667)
  • fixed a bug in hashdecl member initialization in constants (issue 3654)
  • fixed a bug in type handling that could cause a runtime crash (issue 3644)
  • MysqlSqlUtil: fixed a bug where the sequence table name was not respected in MysqlDatabase::getNextSequenceValueImpl() (issue 3641)
  • Schema: fixed a bug where too little information was passed to post schema alignment code (issue 3640)
  • fixed a bug where in-object calls to implicit copy() methods would result in a core dump (issue 3637)
  • Mapper module: fixed a bug where list values could not be passed as a value in non-bulk mode (issue 3611)
  • fixed an error with runtime method call resolution with private:internal methods (issue 3596)
  • PgsqlSqlUtil module: fixed compatibility with PostgreSQL 12 (issue 3589)

Qore 0.9.3.1

Release Summary

Bugfix release; see details below

Bug Fixes in Qore

  • fixed a critical error handling thread resources where if an exception was thrown handling thread resources, user thread resource handlers queued afterwards were not executed (issue 3571)
  • fixed a crash handling recursive user module dependencies with directory-based (split) user modules (issue 3570)
  • fixed an error handling aborted chunked HTTP transfers that can result in a long timeout stalling the I/O thread (issue 3564)
  • added library option constants and functions to allow the TLS v1.3 protocol to be disabled when the library is initialized or at runtime (issue 3561)
  • fixed a bug where different connections on the same Socket object could not be identified; code that relied on Socket::getSocket() is unreliable as the same descriptor can be reassigned (issue 3558)
  • fixed a core dump in FileLineIterator::getFileName() (issue 3555)
  • fixed a race condition in thread resource cleanups where a spurious exception could be raised (issue 3551)
  • RestSchemaValidator: fixed a bug where REST serialization errors in server responses were ignored and a 200 OK response was sent instead (issue 3547)
  • fixed a bug where false positive parse-time matches with a complex list or hash type could be made with incompatible types (issue 3546)
  • astparser module:
    • fixed memory leaks in astparser module (issue 3344)

Qore 0.9.3

Release Summary

Bugfix release; see details below

Fixes That Can Affect Backwards-Compatibility

Complex type fixes in this release have the effect that complex type declarations are not exactly equal to the base types without a complex type restrictions, and also abstract argument type matching with concrete implementations has been loosened to accept nearly identical matches, so that for example an abstract method may declare a parameter with a hash<auto> type which may be implemented by a concrete method with type hash.

New Features in Qore

Bug Fixes in Qore

  • fixed bugs in handling object members assigned to references (issue 3523)
  • fixed bugs in thread-local variable handling and Program destruction (issue 3521)
  • fixed a bug where a crash would result when serializing imported typed hashes (issue 3518)
  • fixed a bug where attempting to serialize a weak references to a serializable object would result in an exception (issue 3515)
  • fixed a bug where new DatasourcePool connections were left in place when calls to DatasourcePool::beginTransaction() would fail with an exception (issue 3509)
  • fixed bugs importing user modules with an injected API in an existing Program container (issue 3504)
  • fixed a memory leak in Serializable::deserialize(string)
  • fixed a memory leak (crash in debug mode) related to deterministic garbage collection (issue 3481)
  • fixed a bug where HTTP redirect messages with a simple path and not a full URL were not processed correctly (issue 3475)
  • fixed a bug where HTTP connections with UNIX domain sockets were sending an incorrect Host: header without URL encoding (issue 3474)
  • fixed bugs affecting injection and Program API management (issue 3461)
  • fixed a bug where a '/' character in an HTTP username would cause a URL to be parsed incorrectly (issue 3457)
  • added optional flags to the following methods to allow them to open file streams in nonblocking mode to handle opening named pipes independently of the writer without blocking: (issue 3451)
  • fixed a bug compiling with openssl with the MDC2 algorithm disabled (issue 3443)
  • fixed a confusing error message with runtime overload type errors where complex type information was missing (issue 3441)
  • fixed parse-time error handling complex types in hashes (issue 3438)
  • fixed many type errors with complex types (issue 3429)
  • fixed inconsistent behavior of references with pseudo-methods (issue 3417)
  • fixed bugs in the return types of Qore::regex_extract() and <string>::regexExtract() (issue 3416)
  • fixed documentation links between dependent modules (issue 3406)
  • fixed a bug where an lvalue with a complex type accepted incompatible assignments from values without complex types if the base type was the same; this fix also ensures that complex type declarations with auto are not treated as identical to the base type without any complex type restrictions, in addition abstract type matching was loosened to accept near matches with parameter types so that ab stract method with a parameter type of hash<auto> can be implemented with a concrete method with a hash parameter type, for example. (issue 3404)
  • fixed a bug where a crash could result when deserializing invalid integer data (issue 3395)
  • fixed a parse type error in initialization using return value of abstract method (issue 3387)
  • fixed a bug where sort functions were incorrectly sorting strings with different lengths (issue 3378)
  • fixed a member initialization bug with imported classes (issue 3368)
  • HttpServer module:
    • shut down dedicated socket conenctions last in order to allow for effective keep-alive implementations with WebSocket for example (issue 3488)
    • fixed a bug where disconnected connections could cause unhandled exceptions to be output in the connection thread (issue 3415)
    • fixed certificate and key errors for HTTPS listeners to generate user-friendly exceptions (issue 3397)
  • Logger module:
  • Mime module:
    • fixed bugs parsing binary data in multipart messages (issue 2936)
  • PgsqlSqlUtil module:
    • fixed comparison of triggers with column restrictions with table alignment (issue 3466)
  • Pop3Client module:
    • fixed the timeout value for upgrading the SSL connection in Pop3Client (issue 3388)
  • QUnit module:
    • allow binary modules to be subjected to dependency injections (issue 3382)
  • RestHandler module:
    • fixed RestHandler losing internal exception info when response was considered invalid by schema validator (issue 3435)
    • fixed RestHandler incorrectly handling Accept header of incoming requests (issue 3426)
    • added debug logging for REST schema validation errors (issue 3410)
  • RestSchemaValidator module:
    • fixed NullRestSchemaValidator not respecting set Content-Type header from RestClass (issue 3427)
  • SmtpClient module:
    • fixed the timeout value for upgrading to SSL connection in SmtpClient (issue 3381)
  • SqlUtil module:
    • fixed quoting of reserved words in column names in table alignment (issue 3400)
    • implemented the AbstractDatabase::getPhysicalSize() method (issue 3385)
  • Util module:
    • fixed a bug parsing nested lists in parse_to_qore_value() (issue 3483)

Qore 0.9.2

Release Summary

Bugfix release; see details below

New Features in Qore

  • qdbg-remote supports an option to provide HTTP headers for WebSocket connections (issue 3350)

Bug Fixes in Qore

  • implemented support for deserializing data from a binary string (issue 3357)
  • fixed a bug with class initialization that could sometimes result in members of parent classes not being initialized when objects were constructed (issue 3355)
  • fixed a bug in the SqlUtil module that could lead to a deadlock when DML methods are used with a datasource pool with connection contention (issue 3352)

Qore 0.9.1

Release Summary

Bugfix release; see details below

New Features in Qore

  • the serialization protocol has been updated to version 1.1; it still reads both binary- and data-serialized data from v1.0
  • added the ListSerializationInfo hashdecl to support serializing and deserializing lists with complex type information
  • new user modules:

Bug Fixes in Qore

  • fixed a bug where the Salesforce rest connection returns 'rest' type instead of 'sfrests' (issue 3346)
  • fixed a bug where an invalid parse exception would be raised with an assignment of a global variable to another global variable with the same name in a different namespace (issue 3337)
  • implemented support for serializing and deserializing complex type information in lists and hashes (issue 3318)
  • fixed bugs handling unassigned lvalues with complex type declarations with the push and unshift operators (issue 3317)
  • fixed a memory leak in copy constructor execution in complex class hierarchies (issue 3312)
  • implemented support for automatically initializing the Qore library from Java when dynamically loaded from the JVM; additionally in this case the jni module is loaded automatically immediately after the Qore library is initialized (issue 3310)
  • implemented support for performing binary searches in binary data by adding the following new pseudo-methods: (issue 3300)
  • Util module fixes:
    • fixed a bug in get_exception_string() with Java exceptions (issue 3304)
  • QUnit module fixes:
    • fixed a bug where tests could not be nested (issue 3306)
  • RestClient:
    • fixed a bug with charset in the RestClient module (issue 3328)
    • fixed default option handling in REST connections including timeout handling (issue 3321)
  • SalesforceRestClient:
    • fixed default option handling in REST connections including timeout handling (issue 3321)
  • SewioRestClient:
    • fixed default option handling in REST connections including timeout handling (issue 3321)
  • WebUtil:
    • fixed a bug when StaticTemplateManager does not respect constructor's parse options in templates (issue 3334

Qore 0.9

Release Summary
This is a major release of Qore with large portions of code subject to extensive optimizations leading to large memory and performance improvements along with more control of Program logic containers, multithreading, and a reflection API. This release breaks binary compatibility with older versions of Qore as well, requiring binary modules to support the new API and ABI.

Changes That Can Affect Backwards-Compatibility

  • Qore classes and functions are now immutable once created; any attempt to add a new user variant to an existing function or method or to add new declarations to an existing class will result in a parse error.
  • Program objects now only support a single complete parse action (Program::parse() or Program::parseCommit()); subsequent attempts to parse code into the same Program object will fail with an exception. If parsing fails due to a parse exception, the Program object is generally no longer usable and must be recreated to be used.
  • Program::parseRollback() is now deprecated; this action removes all user code and most builtin code from the Program object; delete the object instead of using this method
  • the transient keyword has been introduced to support control over object serialization; see also %no-transient

New Features in Qore

Bug Fixes in Qore

  • fixed a bug in parse_url() with single-character hostnames with a port number (issue 3287)
  • fixed a minor bug handling error info in exception handling in the RestClient module (issue 3280)
  • fixed a crash in acquiring a new connection with datasource options (issue 3262)
  • fixed a bug reporting the source location for runtime type errors related to missing return statements (issue 3255)
  • fixed bugs where Datasource::getConfigString() and Datasource::getConfigHash() would require a connection to the server, making it impossible to check option before connecting (issue 3247)
  • fixed a bug with weak references in some assignment expressions (issue 3202)
  • fixed bugs in sprintf(), vsprintf(), and all variants where NOTHING was not treated the same as no value (issue 3184)
  • worked around a potential COW bug in std::string in GNU libdstdc++ 6+ (issue 3179)
  • fixed a bug with simple additional and subtraction with mixed timeout and date values; updated docs that arithmetic operations with timeout values are not recommended and can return unexpected values in some situations (issue 3157)
  • fixed a bug in deterministic garbage collection where Queue objects were not scanned and therefore cycles due to Queue elements would cause a memory and reference leak (issue 3101)
  • fixed a bug where call references did not set the execution context with builtin functions and therefore calls to builtin functions in modules (such as jni) with per-program private data would fail (issue 3024)
  • fixed a bug where rvalue references with complex subtypes could get modified during an assignment (issue 2891)
  • Fixed a bug where class members could be initialized multiple times in a class with multiple inheritance where the same class is inherited multiple times in the hierarchy (issue 2741)
  • Fixed bugs handling abstract methods in complex hierarchies with multiple inheritance (issue 2741)
  • Fixed bugs handling object scope in background expressions (issue 2653)
  • Fixed a bug: hash(list<auto>) where l has an odd number of elements never returns (issue 2860)
  • Fixed a bug where no error is issued when an expression does not have meaning as a top-level statement (issue 2826), and also where such expression is an argument to the background operator (issue 2747)
  • Fixed a bug where the parser does not recognize that a return value of a function call is not ignored if it is an object and its method is immediately called (issue 2863),
  • Fixed a bug where public and private members of classes inherited with private:internal inheritance were not initialized when objects were created (issue 2970),
  • Module fixes:
    • QUnit:
      • fixed error reporting with type errors with number values (issue 2984)

Qore 0.8.13.9

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a bug handling start and end arguments in replace() that would cause a crash (issue 3345)
  • fixed a bug handling invalid DB driver options in datasource creation that could lead to a crash with some drivers (issue 3243)
  • fixed a memory error in internal list handling that could lead to memory corruption and crashes (issue 3206)
  • fixed calls to Dir::list*() methods which failed whenever there was a symlink with a non-existent target in a directory (issue 3192)
  • fixed a bug handling illegal abstract method definitions of special class methods (issue 3126)
  • fixed handling 304 Not Modified responses in the HTTPClient class (issue 3116)
  • fixed a crashing bug in the Transform class when used with encryption algorithms (issue 3111)
  • fixed a crash with multiple hash keys when parsing the hash map operator (issue 3108)
  • module fixes:

Qore 0.8.13.8

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.13.7

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • module fixes:
  • fixed a race condition in ThreadPool destruction that could cause a crash (issue 2906)
  • fixed a hard to reproduce bug with internal runtime type matching that sometimes caused invalid runtime exceptions to be raised with base class constructors (issue 2928)
  • fixed an error handling attach errors to Program objects from foreign threads after the program has been deleted (issue 2950)
  • fixed a bug that would cause a crash if an unknown "Content-Encoding" value were received by the HTTPClient class (issue 2953)
  • fixed a memory leak with binary objects in certain operations such as when reading a file into a binary object (issue 2982)

Qore 0.8.13.6

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.13.5

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a bug where user modules with global variables could not be loaded into Program containers where PO_NO_GLOBAL_VARS was set (issue 2807)
  • fixed a deadlock with RWLock and Condition objects when the read lock is held recursively (issue 2817)
  • module fixes:
    • CsvUtil:
      • implemented the number_format option to allow numbers with alternative decimal separators to be parsed and generated (issue 2806)
    • RestClient:
      • added support for REST requests with binary message bodies; added the "bin" serialization method (issue 2816)
    • RestSchemaValidator:
      • fixed the null validator to handle binary message bodies; fixed issues with "text" serialization with binary message bodies (issue 2816)
    • Mime:
      • fixed a bug in mime_parse_form_urlencoded_string() where repeated elements would be overwriteen by subsequent keys with the same name (issue 2761)

Qore 0.8.13.4

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a bug where hashes and lists with subtype auto were not created correctly with implicit initialization causing excess type stripping which could lead to performance issues with large data structures (issue 2767)
  • implemented a new optional DBI statement method to allow for statement execution only for describing the result set to solve performance issues when describing statements with large data sets (issue 2773)
  • fixed a performance bug by eliminating overzealous and unnecessary internal type stripping (issue 2791)
  • module fixes:
    • CsvUtil:
      • implemented the csvutil_set_global_compat_force_empty_string() function and the compat_force_empty_string CSV parsing option to force "*string" fields with no value to return an empty string when parsing rather than NOTHING for backwards compatibility with very early versions of CsvUtil (issue 2476)
    • Mime:
      • mime_parse_form_urlencoded_string raies a parse exception when there is no value for a key (issue 2760)
    • OracleSqlUtil module changes
      • synonym resolving can fail with duplicated object name (issue 758)
    • SqlUtil:
      • implemented the AbstractTable::getRowIteratorNoExec() method (issue 2773)
    • TableMapper:
      • updated to use the new SQL statement DBI method for efficient execution of queries only for describing result sets with outbound mappers to solve performance problems related to mappers that have statements with large data sets (issue 2773)
      • fixed RawSqlStatementOutboundMapper to be usable without subclassing (issue 2775)

Qore 0.8.13.3

Release Summary
Bugfix release; see details below

New Features in Qore

  • improved debugging support:
    • added support for a Visual Studio Code debug adapter for Qore
    • the debugger can now retrieve sources when running from a remote debug server
    • debugger options can now be set from command line (verbosity etc.)
    • the onAttach() event is now executed synchronously when the program thread context starts
    • the onDetach() event is executed properly when program thread contexts terminate
    • the onStep() now provides the breakpointId value if available
    • the onExit() event was added for greater control over code execution in the debugger
    • the onException() event was improved
    • server commands now support frameid as a parameter
    • added the following methods to support retrieving source code in the debugger:
  • new module:

Bug Fixes in Qore

  • module fixes:
    • QUnit:
      • improved output in assertion failures for strings with special whitespace and for multi-line data structures (issue 2680)
    • WebUtil:
      • made it possible for FileHandler subclasses to add headers to response (issue 2686)
  • HttpServerUtil:
    • improved HTTP log masking to mask fewer false positives when attempting to mask sensitive data (issue 2621)
  • fixed a crashing bug initializing constants with recursive references to code (issue 3027)
  • fixed a crashing bug in the += operator with objects and hashes when %require-types is not in force (issue 2634)
  • fixed a crashing bug in the background operator with non-constant hash expressions with local variable references (issue 2637)
  • worked around an Oracle bug in materialized view creation in the OracleSqlUtil module where when the schema user is missing the CREATE MATERIALIZED VIEW grant the table backing the view is created but the materialized view itself is not created causing future creation actions to fail (issue 2643)
  • implemented support for an optional error-handling method in SQL callbacks in the SqlUtil module to allow SqlUtil to recover from error scenarios in schema creation/alignment (issue 2643)
  • fixed a design bug where an empty list () and an empty hash {} could not be assigned to complex types, leading to excess typing and casting for simple operations (issue 2647)
  • fixed a bug in the map operator with complex types and empty list expressions (issue 2651)
  • fixed a bug where implicitly-declared values of complex "or nothing" types would not be declared with the correct runtime type information (issue 2652)
  • fixed a bug affecting class initialization with out of order initialization (issue 2657)
  • implemented support for the more concise declaration of immediate typed hash values (issue 2675)
  • fixed a bug where a crash would result when evaluating certain expressions in the brackground operator due to a memory error (issue 2679)
  • fixed date formatting output with the Z placeholder to always output the UTC offset as documented (issue 2684)
  • fixed program thread context to return frames properly (issue 2674)
  • fixed an internal memory bug that could cause unallocated memory to be read when creating objects (issue 2712)
  • fixed a memory issue with typed hashes that could lead to a runtime creash (issue 2725)

Qore 0.8.13.2

Release Summary
Bugfix release; see details below

New Features in Qore

  • "thread list", "backtrace all" commands implemented for the debugger (issue 2608)
  • QUnit: overloaded the testAssertionValue() method to support auto/number/float and more verbose output when a difference in number/float values is found (issue 2556)
  • qdbg-remote supports ConnectionProvider connections (issue 2613)
  • new method: Breakpoint::getProgram()

Bug Fixes in Qore

Qore 0.8.13.1

Release Summary
Bugfix release; see details below

New Features in Qore

  • the sqlutil script has been updated with the –select option to allow dumped table rows to be filtered (issue 2509)

Bug Fixes in Qore

  • fixes in modules:
    • astparser module fixes:
      • fixed memory leaks in AstParser::parseFile() and AstParser::parseString() methods (issue 2261)
      • fixed incorrect flex code regarding parse options leading to segfaults (issue 2262)
    • DebugCmdLine module fixes:
      • fixed value setting to process all remaining arguments on the command line (issue 2294)
    • DebugCmdLine module fixes:
      • the debugger should report ambiguous partial matches as an error (issue 2292)
    • MailMessage module fixes:
      • fixed Message::addBody() with no body present (issue issue 2360)
    • Mapper module fixes:
      • fixed a bug in the STRING-TOO-LONG exception (issue 2405)
    • PgsqlSqlUtil module fixes:
      • fixed a bug where default column values were compared incorrectly leading to false positives when comparing and aligning DB schemas (issue 2527)
    • Qdx module fixes:
    • QUnit fixes:
      • added missing comparison methods (issue 1588):
        • Test::assertRegex()
        • Test::assertNRegex()
        • Test::assertNeq()
        • Test::assertNeqSoft()
        • Test::assertGt()
        • Test::assertGtSoft()
        • Test::assertGe()
        • Test::assertGeSoft()
        • Test::assertLt()
        • Test::assertLtSoft()
        • Test::assertLe()
        • Test::assertLeSoft()
        • Test::assertNothing()
    • RestHandler module fixes:
      • updated to return a 400 Bad Request error when REST schema validation fails on messages received issue 2344)
      • updated to return a 400 Bad Request error when there are string encoding errors with messages received (issue 2398)
      • updated to return a 404 Not Found error when REST subclass does not exist (issue 2405)
      • updated to return a 400 Bad Request error when ENCODING-CONVERSION-ERROR occurs during request parsing (issue 2543)
    • RestSchemaValidator module fixes:
      • updated docs for AbstractRestSchemaValidator::parseRequest() to reflect how validation exceptions should be raised for proper error reporting (issue 2344)
      • fixed handling of messages with non-object (i.e. non-hash) bodies (issue 2366)
    • SqlUtil module changes
      • implemented support for custom column operators (issue 2314)
    • OracleSqlUtil module changes
      • implemented support for chained synonyms (issue 2408)
      • allow to use DBA_* views instead of ALL_* if possible (issue 2418)
    • Swagger module fixes:
      • fixed handling of string type date and date-time formats (issue 2341)
      • fixed example value for binary type (issue 2342)
      • fixed serialization of date/time values (issue 2349)
      • updated to return a 400 Bad Request error when REST schema validation fails on messages received issue 2344)
      • fixed handling of non-string enum types (issue 2364)
      • fixed confusing error messages with invalid parameter types (issue 2365)
      • fixed handling of messages with non-object (i.e. non-hash) bodies (issue 2366)
      • fixed handling of optional parameters (issue 2369)
      • fixed handling of non-string query parameters (issue 2388)
      • fixed a bug where string value constraints were only enforced in requests but not responses (issue 2396)
      • fixed a bug where invalid date, binary, and byte values would cause a 500 Internal Server Error response to be returned instead of a 400 Bad Request error (issue 2397)
      • fixed a bug where date values were formatted incorrectly in Swagger responses (issue 2409)
      • fixed a bug which made it impossible to send data with other content/mime types than json, yamlrpc, FormUrlEncoded or MultipartFormData (issue 2497)
      • fixed handling of string/binary values (issue 2505)
      • fixed a bug where consumes property of operations was sometimes ignored (issue 2507)
      • fixed parsing of responses without Content-Type header (issue 2517)
      • fixed path matching for paths not beginning with a slash (issue 2516)
    • TableMapper module fixes:
      • fixed issues where where description fields of input and output records for automatically-generated options did not reflect column comments and could not be overridden with user input (issue 2520)
  • fixed bugs affecting debugging matching function/method variants and finding statements with special methods and with complex types (issue 1865)
  • fixed a bug in qpp generating hashdecl code in a specific namespace (issue 2255)
  • fixed an error in a hashdecl documentation example (issue 2299)
  • made C++ APIs for complex types for modules public (issue 2271)
  • fixed inconsistencies in the behavior of the range operator (..) and the square brackets operator [] with lists and ranges between immediate evaluation and lazy functional evaluation and aligned the behavior of the operators among supported data types with the remove and delete operators (issue 2260)
  • fixed a bug handling statement indices with parse errors (issue 2312)
  • fixed too-agressive class hierachy checks that disallowed legal hierarchies where the same base class appears more than once in the hierarchy (issue 2317)
  • fixed a crashing bug in the background operator when the object in context goes out of scope with the thread and an exception is thrown (issue 2319)
  • fixed sending duplicate headers when header hash keys differ only in case; headers that differ only in case will be overwritten by the last header in the hash with a matching name with a case-insensitive search (issue 2340)
  • fixed q_absolute_path_windows to correctly recognize relative Windows paths beginning with a drive letter (issue 2377)
  • fixed a bug in private:internal in method execution within a class hierarchy in some cases (issue 2380)
  • fixed an obscure bug handling runtime errors in code calls with a variant matched at parse time where a runtime exception could occur (issue 2392)
  • improved breakpoints (enabled by default), extended help texts, load/save debug history and session (issue 2401)
  • fixed a bug in an error message regarding binary module signal assignments (issue 2439)
  • added C++ functions to allow binary modules to allocate and deallocate multiple signals atomically (issue 2440)
  • eliminated a warning in a header file when building with g++ 7+ (issue 2449)
  • implemented a fix in qdbg to resume any blocked threads before exiting to ensure a clean and correct shutdown of the debugger; fixes a problem when the process ould freeze on quit (issue 2472)
  • fixed bugs in Windows builds (issue 2529)

Qore 0.8.13

Release Summary
Major new features and bug fixes including input and output stream support and sigificant new functionality including several new modules.

Changes That Can Affect Backwards-Compatibility

  • fixed broken continue and break statements that were accepted anywhere in the source and behaved like a return statement; now such statements outside a loop context will result in a parse exception; to get the old behavior, use %broken-loop-statement in your source code
  • fixed broken reference and *reference type restrictions which had no effect prior to this release; to get the old behavior, use %broken-references in your source code
  • the random number generator is always seeded with a random number when the Qore library is initialized; to get a predictable sequence from rand(), you must explicitly seed the random number generator by calling srand() with a predefined seed number
  • the synchronized keyword now operates differently depending on the context; synchronized functions have a global reentrant lock associated with the function (as in previous versions of Qore), whereas now synchronized normal class methods share a reentrant lock associated with the object, while synchronized static class methods share a reentrant lock associated with the class itself. This aligns Qore's synchronized behavior with that of Java and [MethodImpl(MethodImplOptions.Synchronized)] .NET/CLR (issue 894).
  • classes may not have the name "auto" due to the introduction of this identifier as a special type name
  • a new keyword hashdecl has been introduced to support type-safe hash declarations

New Features in Qore

Bug Fixes in Qore

  • fixed a bug causing AbstractQuantifiedBidirectionalIterator not being available (issue 968)
  • BulkSqlUtil module fixes:
    • fixed the module to work properly even with DB drivers that do not support parameter array binding (issue 1154)
  • CsvUtil module fixes:
    • fixed a bug in an error message validating input data (issue 1062)
    • added an exception when detected headers do not match the fields option (issue 2179)
  • HttpServer module fixes:
    • added logic to attempt to mask passwords in log messages (issue 1086)
  • HttpServerUtil module fixes:
    • fixed a bug where the msg arg to AbstractAuthenticator::do401() was ignored (issue 1047)
  • RestHandler module fixes:
    • added logic to allow sensitive data to be masked in log messages (issue 1086)
  • SqlUtil module fixes:
    • fixed a bug in update and upsert statement generation when the given data does not have enough columns to use the unique index found, an error message is generated that contains all the columns names instead of just the column names required by the index (issue 1013)
  • WebSocketClient module fixes:
    • fixed a thread lock starvation race condition (issue 2130)
  • UTF-16 fixes:
  • fixed a bug where break and continue statements were accepted outside of loops (issue 976)
  • fixed a bug compiling on Solaris SPARC with g++ where MPFR_DECL_INIT() is compiled incorrectly with -O1 or greater (issue 958)
  • fixed a bug causing an infinite loop in decompression functions (issue 966)
  • fixed an issue where an internal C++ API (QoreProgram::parseCmdLineDefines()) performed a needless copy of a data structure (issue 1099)
  • fixed a stack corruption bug with asynchronous I/O on UNIX systems with ReadOnlyFile methods (issue 1106)
  • fixed bugs with inconsistent conversions of int, float, and boolean values to date/time values, now they are all converted uniformly to relative date/time values (issue 1156)
  • fixed a bug where Qore allowed code to be declared both public and private without a warning (issue 1187)
  • fixed a bug where the instanceof operator would return True with objects that did not publically inherit the given class or where the given class is not accessible (issue 1191)
  • fixed a bug in qpp support of the 'final' class flag (issue 1222)
  • fixed a bug where the + operator provided access to private members from outside the class (issue 1209)
  • fixed a bug where different overloaded method variant resolution rules were used at parse time (best match in hierarchy) and runtime (best match in first matching class) in a class hierarchy (issue 1229)
  • fixed a bug where exceptions in base class constructor calls did not reflect the actual source location (issue 1230)
  • fixed a bug where runtime function/method variant matching was incorrectly biased towards default matches for missing arguments (issue 1231)
  • fixed bugs where calls to Socket::upgradeClientToSSL() and Socket::upgradeServerToSSL() were ignored with no exception thrown if the socket was not connected (issue 1258)
  • fixed a bug where a closure created in an object scope could not be called if the object had been deleted, even if the closure did not refer to the object (issue 1303)
  • fixed a bug where ord() would return negative numbers for bytes with the high bit set with compilers where char is the same as signed char (issue 1385)
  • fixed a bug where int(number) returned rounded value instead of the integer part (while int(float) behaved correctly; also cf. initializing a softint value from a number vs. from a float) (issue 1463)
  • File::read() now uses character semantics for the length argument (issue 1548)
  • fixed a bug with strongly-typed lvalue assignments with classes created in different Program objects (issue 1551)
  • fixed a bug where an ASCII string and the same string in a different encoding and with diacritics could incorrectly be marked as equal (issue 1579)
  • fixed bugs in HTTPClient methods where string message bodies were not converted to the object's character encoding before transmission (issue 1813)
  • fixed a bug in the reference and *reference assignment restrictions; previously any value was accepted, now only references are accepted as the initial assignment values (issue 1819)
  • fixed a bug in handling the SqlUtil::BLOB type in the FreetdsSqlUtil module (issue 1852)
  • fixed a bug in overloaded call variant matching where missing arguments were counted towards the match (issue 1897)
  • fixed many bugs where parse-time errors could be reported at an incorrect source location; parse-time error location reporting has been completely overhauled and reimplemented for correctness (issue 1930)
  • fixed a bug where code signatures would accept parameter variables without "$" signs even when %allow-bare-refs was not in effect (issue 1941)
  • fixed memory leaks in the scanner related to EOF conditions (issue 1976)
  • rewrote Qore functions Qore::gethostbyname(), Qore::gethostbyname_long() and Qore::gethostbyaddr() to use standard C functions getaddrinfo(3) and getnameinfo(3) internally instead of the deprecated gethostbyname(3) and gethostbyaddr(3) (issue 1952)
  • fixed cmake builds on Darwin (issue 1980)
  • fixed a bug where immediate date-time values were not marked with their type at parse time (issue 2001)
  • fixed a bug where the *data type restriction would allow all types to be assigned at runtime (issue 2002)
  • Qore::RangeIterator::constructor(int) and Qore::xrange(int) were updated; the second arguments were removed to avoid ambiguity with the other overloaded variants (issue 2016)
  • fixed a bug where Qore::replace() could get in an infinite loop with arguments with embededed nulls (issue 2098)
  • fixed a bug in regular expression extraction where an infinite loop could occur (issue 2083)
  • fixed a bug where a call reference to an object method that crosses Program boundaries could result in a core dump when called due to an error managing thread-local data (issue 2145)
  • fixed crashes in scanner due to EOF in comments (issue 2175)

Qore 0.8.12.12

Release Summary
Bugfix release; see details below

New Features in Qore

  • added the HAVE_DSS constant to indicate if the outdated DSS(), DSS1(), DSS_bin(), DSS1_bin(), DSS_HMAC(), and DSS1_HMAC() functions are available in the opnessl library used to compile Qore

Bug Fixes in Qore

  • fixed a bug handling argv in base class constructor execution (issue 2030)
  • fixed a bug handling the connection status in the HTTPClient class (issue 2058)
  • fixed building with openssl 1.1+ (issue 2135)
  • fixed binding more than one wilcard port on a specific address in the HttpServer module (issue 2155)
  • fixed a bug in SqlUtil with column aliases that are reserved words (issue 2163)
  • fixed a memory bug in the splice operator with a binary operand (issue 2303)
  • fixed a bug where calling any SQLStatement method in another thread with an active connection from a DatasourcePool causes a crash (issue 2334)
  • fixed a bug in RestHandler regarding inconsistent handling of URI parameter arguments; the "action" key was only removed from the ah hash when there were no other arguments, introducing an inconsistency in argument handling in REST services (issue 2479)
  • fixed a bug where ENCODING-CONVERSION-ERROR exceptions were not thrown with newer GNU iconv libraries with an API change (issue 2500)

Qore 0.8.12.11

Release Summary
Bugfix release; see details below

New Features in Qore

Bug Fixes in Qore

  • fixed documentation regarding escaping of characters in strings and added a parse exception in case of trying to escape octal values in range 400-777 (issue 50)
  • fixed a crashing bug where Datasource::getConfigString() was called without a connection, also could crash in an implicit internal call to this method with the DatasourcePool class when connections were lost and the warning callback should be called (issue 1992)
  • fixed a bug where Datasource::getConfigHash() returned different values depending on if the object was connected or not (issue 1994)

Qore 0.8.12.10

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.12.9

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a memory leak where references participate in recursive references (issue 1774)
  • fixed a build issue with clang++ (issue 1768)
  • fixed a memory leak in the Queue copy constructor when the Queue was used in other objects (such as an event queue, etc; issue 1749)
  • Mapper module fixes:
    • fixed bugs handling the allow_dot and allow_output_dot options (issue 1690)
    • fixed TableMapper bugs introduced in Qore 0.8.12.7 (issue 1754)

Qore 0.8.12.8

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a memory leak in %try-module error handling (issue 1690)
  • fixed a bug in trunc_str() when the string has an invalid multi-byte character at the end of the string and the string is exactly the byte width requested (issue 1693)
  • fixed a bug where ReadOnlyFile::getchar() did not respect character semantics as documented (issue 1547)
  • OracleSqlUtil module fixes:
    • fixed a bug in character_semantics for standalone column (issue 1688)
  • Mapper module fixes:
    • fixed a bug in handling "list mode" data such as submitted by InboundTableMapper::queueData() (issue 1736, bug introduced in Qore 0.8.12.7 with the fix for issue 1626)
  • SqlUtil module fixes:
    • fixed schema alignment skipping column with name "driver" (issue 1684)
    • fixed sqlutil schema management: functional indexes are rejected without () in name (issue 1610)
  • TableMapper module fixes:
    • fixed a bug in handling "list mode" data with optimized inserts (issue 1736, bug introduced in Qore 0.8.12.7 with the fix for issue 1626)
  • WebSocketClient module fixes:
  • WebSocketHandler module fixes:
  • WebSocketUtil module fixes:
  • fixed a bug where a type conversion error in an lvalue assignment could generate a confusing unrelated runtime exception (issue 1697)
  • fixed a bug where invalid characters in the port specification in a URL were ignored (issue 1728)
  • fixed a bug with SSL socket communication the remote closing the connection during a send operation could cause the current thread to go into an infinite loop consuming 100% CPU (issue 1729)
  • fixed a bug in the HashListIterator class iterating hashes with a mix of lists and single values such as used by bulk DML binds; now the single values will appear as the current value for all list elements as per the original design instead of throwing a runtime exception (issue 1738)

Qore 0.8.12.7

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed bug in internal string generation with size_t arguments that could cause invalid data to be output or crashes on 32-bit platforms (issue 1640)
  • fixed a runtime memory leak and invalid runtime behavior with undetected recursive lvalue references (issue 1617)
  • improved prompt collection performance with large graphs of objects by eliminating additional unnecessary graph scans, resulting in further large performance improvements in the garbage collector (issue 1363)
  • improved InboundTableMapper::queueData() performance (in the TableMapper module) when used with data in hash of lists format to use bulk DML in input and output without internal data conversions (issue 1626)
  • OracleSqlUtil module fixes:
    • worked around ORA-22165 from op_in() caused by Oracle's limit on number of collection elements (issue 1660)
    • fixed a bug in the force option (i.e. cascade) for dropping types (issue 1683)
  • improved %try-module error reporting and documentation (issue 1648)

Qore 0.8.12.6

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a bug in Qore::parse_url() parsing single-character hostnames (issue 1524)
  • fixed a bug where PO_LOCKDOWN was not set when parsing init and del attributes in user module headers (issue 1535)
  • fixed a bug parsing exception catch block parameter errors (in debug builds only; issue 1558)
  • fixed a bug dereferencing binary values with the [] operator; the behavior now corresponds to the documentation (issue 1566)
  • fixed a bug that would result in a crash if a method were declared both static and abstract (issue 1590)
  • fixed performance issues with the Mapper module (and by extension the TableMapper module) for mappers with many identity (i.e. 1:1) and constant mappings (issue 1620)
  • fixed a bug in the BulkInsertOperation class in the BulkSqlUtil module where inserts would fail or silently insert invalid data in the second or later blocks when constant hashes were used (issue 1625)

Qore 0.8.12.5

Release Summary
Bugfix release; see details below

New Features in Qore

  • added the SalesforceRestClient module for communicating with Salesforce.com using the REST APIs
  • module SqlUtil
    • has support for native default values in tables (issue 1428)
    • has support for Oracle named types (eg. spatial types) for Schema.qm and SchemaReverse.qm. (issue 1465)

Bug Fixes in Qore

Qore 0.8.12.4

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

  • fixed a reference bug in the Queue class introduced in the last release (issue 1309)
  • fixed a bug where database types could not be correctly aligned if they had dependencies (issue 1314); entailed updates in the following modules:
  • fixed a bug in trunc_str() where an infinite loop could be triggered with certain arguments and multi-byte character encodings (issue 1327)
  • improved prompt collection performance with larger graphs of objects by eliminating unnecessary graph scans made during object method calls (issue 1363)
  • fixed bugs in date(string) and date(string, string) where invalid input data was ignored and invalid dates were returned (issue 1369)
  • CsvUtil module:
    • fixed a bug in AbstractCsvIterator::identifyTypeImpl() generating an error message (issue 1355)
  • MailMessage module:
    • fixed a bug using the default encoding in Message::attach() (issue issue 1352)
  • SqlUtil module:
    • fixed the ignored character_semantics column option in schema alignmed (issue 1379)
    • implemented the cop_length() column function (issue 1395)
  • OracleSqlUtil module:
    • OraclePackage attribute body_src is now public to access package bodies
  • Qorize module:
    • Qorize module: new qorize_val() set of functions; qorize_named() introduced; qorize tests
  • TableMapper module:
    • fixed runtime option propagation to TableMapper::SqlStatementMapperIterator from TableMapper::AbstractSqlStatementOutboundMapper::iterator() (issue 1418)
    • fixed SqlStatementMapperIterator::getCount() (issue 1417)
    • added the following methods:
      • TableMapper::AbstractSqlStatementOutboundMapper::getRowIterator()
      • TableMapper::InboundTableMapper::iterator()
      • TableMapper::InboundTableMapperIterator::getRuntime()
      • TableMapper::InboundTableMapperIterator::replaceRuntime()
      • TableMapper::InboundTableMapperIterator::setRuntime()
      • TableMapper::SqlStatementMapperIterator::getRuntime()
      • TableMapper::SqlStatementMapperIterator::replaceRuntime()
      • TableMapper::SqlStatementMapperIterator::setRuntime()
  • QUnit module:
    • fixed showing the assertion location when there are test modules on top of QUnit (issue 1046)
  • fixed inconsistency between list splice operator and splice function (issue 1380)

Qore 0.8.12.3

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.12.2

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.12.1

Release Summary
Bugfix release; see details below

Bug Fixes in Qore

Qore 0.8.12

Release Summary
Major new release with major new features and bug fixes as well as packaging fixes:
  • added support for deterministic garbage collection
  • standardized function naming convention
  • new functions, methods, constants, operators, and user modules
  • greatly improved support on Windows

Changes That Can Affect Backwards-Compatibility

  • fixed broken list parsing; in previous releases, Qore's parser re-wrote lists without parentheses used as top-level statements with certain assignment operators (=, +=, -=, *=, and /=, but not with others) so that statements like list l = 1, 2, 3; were valid assignments. Due to operator precedence, such statements should normally be interpreted as (list l = 1), 2, 3;, which is not a valid expression. Not only were the rules applied with only some assignment operators, but such lists were only rewritten if used as top-level statements, therefore the rules were applied inconsistenctly depending on where the expression was located in the parse tree. As of Qore 0.8.12, these inconsistencies have been eliminated by default from Qore; all lists are processed according to the precedence rules defined in Operators. This could break old code that relied on the old, broken behavior. To get the old behavior, use the %broken-list-parsing parse directive.
  • fixed broken int and softint assignments; previously runtime type errors with these type restrictions were ignored and all values were silently converted to integers for the assignment, now runtime type errors are thrown according to the original design. Parse errors are detected as before. This could break old code that relied on the old, broken behavior. To get the old behavior, use the %broken-int-assignments parse directive.
  • fixed broken multi-character operator parsing; the Qore parser has been updated to no longer accept multi-character operators with whitespace between the chacters making up the operator; it is believed that this was never used and simply caused the parser to be needlessly complicated and caused Qore to be less compatible with other languages. To get the old behavior, use the %broken-operators parse directive.
  • the push, unshift, pop and shift operators now throw an exception when their first operand is not a list and %strict-args is in effect

New Features in Qore

Bug Fixes in Qore

  • fixed format of octal constant - there was an error if a string contained octal constant that is shorter than 3 digit
  • HttpServer module fixes:
    • fixed a bug setting the response encoding in HttpServer::setReplyHeaders() where the Socket encoding was not set properly and therefore the encoding in the Content-Type in the response header did not necessarily match the encoding of the response
    • fixed a socket / connection performance problem with HTTPS listeners where the SSL connection was being negotiated inline with the accept instead of in the connection thread, thereby blocking new connections from being accepted
    • fixed bugs where URI strings were improperly encoded and decoded (also fixed in the RestClient module)
    • fixed a bug in the HttpServer module where chunked sends were not received and decoded properly in all cases for handlers that did not explicitly handle chunked messages
    • fixed a bug in HttpServer::addListener() with an integer argument; a UNIX socket was opened instead of a wildcard listener on the given port
    • fixed typos causing bugs in HTTP error logging (issue 308)
    • fixed a bug formatting IPv6 host addresses in the return value to HttpServer::http_get_url_from_bind() (issue 821)
  • RestClient module fixes:
    • fixed bugs where URI strings were improperly encoded and decoded (also fixed in the HttpServer module)
    • fixed a bug where URI paths were sent as relative paths instead of absolute paths
    • fixed issues where multiple leading "/" chars were sometimes present in the request URI path
    • fixed an issue where a trailing "/" char was sometimes added to the request URI path (issue 899)
  • CsvUtil module fixes:
    • fixed a bug where the "format" field option was not usable with fields assigned type "*date"
    • fixed the default field type as "*string" (from "string") to avoid parsing and outputting empty strings for missing input data
  • Schema module fixes:
    • AbstractSchema::combineOptions() fails when an option variable contains NOTHING instead of a valid hash
    • fixed a bug with "insert-only reference data" with the verbose option; the upsert strategy was changed to UpsertSelectFirst which means that insert-only reference data could also be updated
    • fixed a bug where it was not possible to provide Database options when creating schemas (issue 501)
  • Mapper module fixes:
    • moved field length checks after all transformations have been applied
    • fixed bugs in the "timezone" and "input_timezone" options, documented those options
    • fixed a bug where "constant" field tags assigned to a value that evaluated to boolean False were not recognized (issue 610)
  • SqlUtil module fixes:
    • fixed a bug with queries using a desc argument with the orderby query option with multiple sort columns; the "desc" string was added only to the last column but should have been added to all columns
    • fixed a bug where foreign key constraints with supporting indexes were not tracked and therefore schema alignment on DBs that automatically create indexes for foreign key constraints would fail
    • fixed a bug where driver-specific objects were not included when dropping a schema
    • fixed a bug in subquery handling where bind-by-value arguments from the subquery were lost
    • fixed a bug in the partition by/over operator where column names as given in the query argument hash were not properly recognized
    • fixed a bug in schema alignment; when aligning a schema and an index supporting a PK constraint is introduced in the new schema, the alignment would fail when a constraint is attempted to be disabled that doesn't exist
    • fixed a bug generating select statements for tables accessed through a synonym when used with join clauses; previously inconsistent schema prefixes could be used which could cause errors parsing the SQL statements generated
    • fixed a bug where the AbstractTable lock was held while executing SQL to determine the upsert strategy to use with UpsertAuto
    • fixed a bug where complex bind values as hashes (such as used by the pgsql and oracle drivers) were rejected by SqlUtil (issue 494) when updating
    • fixed a bug where wildcard columns in join tables were not working (issue 499)
    • fixed a bug in "op_in()" where invalid SQL was generated with an argument of 0 (issue 500)
    • fixed bugs in cop_seq() and cop_seq_currval() (issue 624)
    • fixed a bug in join_inner() where the cond argument was ignored (issue 645)
    • fixed "uop_lower()" and "uop_upper()" operators to allow nesting (issue 657)
    • fixed a bug where SqlUtil was generating invalid SQL for some DBs where a wilcard was used with explicit column names (issue 708)
    • fixed a bug where updating an index without any source constraints caused an invalid exception to be raised (issue 768)
    • fixed a bug in AbstractTable::update() with sequence operators (issue 942)
  • OracleSqlUtil module fixes:
    • fixed a bug where column names that are reserved words were not quoted in generated SQL
    • fixed bugs in cop_seq() and cop_seq_currval() (issue 624)
  • PgsqlSqlUtil module fixes:
    • fixed a bug in PgsqlTable::tryInsertImpl(); added an explicit "begin" call to make the savepoint work with PostgreSQL 9.3+ servers
    • fixed a bug retrieving foreign constraints; columns were not guaranteed to be returned in declaration order
    • fixed a bug handling tablespaces in unique constraints
    • fixed a bug handling "time" columns; they were being issued as "time6" instead of "time(6)" (issue 385)
    • fixed support for the following datatypes and aliases: "bit", "bit varying", "char", "character", "character varying", "char varying", "oid", "varchar"
    • fixed bugs in cop_seq() and cop_seq_currval() (issue 624)
  • MysqlSqlUtil module fixes:
  • WebUtil module fixes:
    • fixed a bug where template programs with Qore::PO_ALLOW_BARE_REFS set did not work
    • fixed a bug serving index files in FileHandler::tryServeRequest() where index files could be incorrectly served with a "204 No Content" response (issue 616)
  • WebSocketHandler module fixes:
    • fixed a bug where the connection object was deleted when the connection closes which could cause excess exceptions in multithreaded server code
    • added the WebSocketConnection::connectionClosed() method to be called when the connection is closed
  • WebSocketClient module updates:
    • updated module to version 1.3
    • ignore SOCKET-NOT-OPEN errors when closing (server already closed the connection)
  • RestHandler module fixes:
    • fold all possible arguments in the REST request body into the argument hash so that complex REST requests can be made with clear URI strings
    • fixed a bug where an error calling an internal nonexistent method would be reported with an incorrect error message
    • send errors are now reported in the AbstractRestStreamRequestHandler object so they can be properly logged (issue 734)
    • unknown REST class errors with the base class are now reported consistently like all other such errors (issue 859)
    • fixed an issue where request URI paths with multiple consecutive "/" chars were handled incorrectly (issue 900)
  • Util module fixes:
    • fixed normalize_dir_windows() handling of UNC paths (issue 813)
  • fixed a memory error in error-handling with type errors when parsing user module headers that could cause a crash
  • fixed a memory leak in Socket::setWarningQueue(): when a callback argument is used, the argument can be leaked when the Socket is destroyed
  • fixed a bug where the HTTPClient class did not send the X.509 certificate and private key when making a client SSL connection
  • fixed a bug in the ThreadPool class where an error in shutdown handling could cause a crash in rare conditions when ThreadPool methods are called while the pool is shutting down
  • fixed a crashing bug initializing some lvalues with type restrictions; affected static class variables at least
  • fixed a bug where a class calling an overridden method in a base class constructor that referred to a member that should have been initialized in the subclass would be executed before the subclass's members were initialized causing the method call to fail
  • fixed a memory leak in classes with multiple inheritance and base classes that are inherited multiple times with member initialization
  • fixed a bug in the %include and %append-module-path parse directives where relative paths were not calculated from the script's directory but instead were calculated from the current working directory, causing such paths to fail
  • fixed a bug in Qore::get_qore_library_info() that could cause a crash due to treating the Build attribute as a string when it was an integer
  • fixed a bug in the divide-equals (/=) operator where an exception was not thrown when an operand of zero with arbitrary-precision numeric arguments is used
  • fixed a bug where the connection mode would be reset for every connection in the Qore::FtpClient class
  • fixed a bug in the Qore::FtpClient class where connection problems in the data channel when executing certain FTP commands could cause a crash due to missing error checking
  • fixed a bug in Qore's internal strcasestr() function on platforms that do not support this function (ex: Solaris) that could result in a crash
  • fixed a bug in Qore where string data formatted with %n, %N, or %y could be added to another string with a different character encoding without any automatic conversions, therefore resulting in an improperly-encoded string
  • fixed a crash when parsing when parsing function, method, or closure arguments when either of the duplicate-local-vars or duplicate-block-vars warnings are set due to an error handling thread-local variable info in parse initialization
  • fixed a bug where code with mixed coding styles (old and new) could result in invalid parse errors when parsing base class constructor calls to a base class defined in another coding style
  • fixed a bug where an HTTP response with an unknown Content-Encoding header would cause a crash
  • fixed a memory error with receiving HTTP chunked data with receive callbacks where the buffer object was reset with reference counts > 1
  • fixed a bug in the FtpClient class where socket errors would not cause the connection to be closed automatically and therefore further use of the object required a manual disconnect even though the object supports transparent auto-reconnection
  • fixed a bug where conversions from float to number would introduce inaccuracy in the arbitrary-precision number; ex: 737.38.toNumber() -> 737.3799999999999954525264911353588104248
  • fixed a bug where %requires would fail loading a user module inside a %try-module block
  • fixed a bug in Qore::Program::importClass() where the import would fail if a namespace-justified class name was given and any element of the namespace path didn't already exist in the target whereas the same import would succeed if the namespace were omitted in the call
  • fixed bugs in Qore::Program::importClass(), Qore::Program::importFunction(), and Qore::Program::importGlobalVariable() when namespace-justified arguments were given, in this case when namespaces were created in the target, the internal root namespace index was not updated so the imported objects could not be found with namespace-justified references until the root indexes were updated
  • fixed a bug in the %requires directive where relative paths were not calculated from the script's directory but rather from the current working directory
  • fixed various bugs in path handling on Windows in the following areas:
  • fixed a bug in parsing constant value assignment expressions where such expressions could use or instantiate classes with uncommitted changes and therefore a crash could result
  • fixed a bug in user module initialization and destruction where call references were not accepted, contrary to the documentation and design goals
  • fixed a bug in Qore::Socket::acceptSSL() and Qore::Socket::connectSSL() where the timeout argument was not respected for SSL protocol negotation by implementing non-blocking I/O support for the internal SSL calls for upgrading the socket connection
  • fixed a memory leak in exception handling in the Qore::FtpClient::put() method (thanks to nros)
  • fixed a memory error in string handling in the Qore::FtpClient class's FTP response handling code
  • fixed a bug in aligning table data in the sqlutil example program
  • fixed a bug when loading modules by a path argument; if the module is already loaded, then do not throw an exception
  • adjusted the stack guard buffer for x86_64 from 20K -> 32K which solved some rare crashes related to stack exhaustion (ex: make check works consistently now on x86_64 Linux)
  • fixed a bug handling HTTP send callbacks that returned zero-length strings and binary objects which would cause invalid chunked data to be sent violating the HTTP protocol
  • fixed a bug in the DatasourcePool::getServerVersion() method where the connection to the server was not guaranteed to be in place before the call, in case of connection errors in the pool a crash could result
  • fixed a crash in Qore::FileLineIterator::copy() when no eol attribute is set
  • fixed a bug importing invalid user modules with no module declaration
  • fixed bugs in Qore::Socket::accept() and Qore::Socket::acceptSSL() where the SSL configuration was not copied to the new Qore::Socket
  • fixed some object encapsulation violation bugs where access to methods of a privately-inherited class was allowed from a subclass in certain situations
  • fixed inconsistent object encapsulation enforcement with method references; if a reference to a method is created inside the class, then when executed the call inherits the access rights at the time of creation
  • fixed inconsistent thread gating for code data structures in Program containers that could have theoretically lead to crashes in Program containers that parse code while threads are running
  • fixed a bug in Qore::Program::importFunction() with function names with a namespace path
  • fixed a bug in closure calls when a closure is called from within a closure and referes to closure-bound locally variables in the internal closure call which would previously result in a crash
  • fixed a parse-time memory leak in call reference calls when the callable object is resolved from a class constant
  • fixed a bug in maintaining the conditional compilation status when parsing %include directives and %requires directives with user modules
  • fixed an obscure bug when a thread terminates in a Program object after the Program container itself has already been deleted where the termination would hang while waiting for the Program's thread count to reach zero while the last thread doing the waiting also held the last thread reference
  • fixed a bug where incompatible class definitions were not verified at parse time which could cause a crash in debug builds and unpredictable behavior in non-debug builds
  • fixed a race condition in finalizing thread-local data in Program objects during Program destruction that could lead to a runtime crash
  • fixed a crash when user modules have recursive dependencies
  • fixed a bug with %push-parse-options when used multiple times in the same file; now multiple appearances of this parse directive are ignored
  • fixed a bug initializing static class variables in the parse commit phase where a crash could result due to an error in managing parse commit dependencies
  • fixed Qore::is_writable():
    • on Windows when used with a directory
    • on UNIX to return a value for the current permissions the program is running under
  • fixed a bug in Qore::regex_extract() and in the Regular Expression Pattern Extraction Operator where the result buffer was not resized when it was too small, limiting regular expressions to nine subpatterns; the maximum has been raised to between 90 and 100 before an exception is raised (since the subpattern buffer is allocated on the stack, we need to enforce a limit)
  • fixed a bug with the cast<>() operator where compatible classes were not recognized at runtime that would otherwise be recognized correctly without the cast
  • fixed the return type in Qore::getcwd() to *string
  • fixed a bug in the return statement where the runtime return type was used at parse time which did not work when parsing embedded code
  • fixed a bug validating return values in method evaluation that could lead to a qore crash
  • fixed a bug in the %requires directive when applied to builtin features where code to manage user module dependencies was inappropriately applied
  • fixed a bug nesting 3 levels or more of parse conditionals (%ifdef and %ifndef) where the conditional parse state could be lost (and an assertion was made in debug mode)
  • fixed a bug where ==, >, and < operators applied type precedence incorrectly when applying optimizations at parse time in relation to arbitrary-precision numeric values
  • fixed a static memory leak in the parser handling out of line method declarations
  • fixed a bug in handling socket disconnection errors in SSL operations where the SSL helper object was deleted and then used causing a crash
  • fixed a bug where Deprecated List and return-value-ignored warnings were reported at the incorrect source location
  • fixed a bug in Qore::set_thread_init() where thread initialization did not occur when foreign threads attached to a Qore::Program object with thread initialization set
  • fixed a bug in call references and objects by replacing string references to the containing Program object with weak references which solved a recursive reference / memory leak issue
  • fixed a memory leak when a thread init call reference was used with Qore::Program objects
  • fixed bugs in Qore SSL socket handling when the remote connection is disconnected while performing an SSL upgrade (client or server) that could cause a crash
  • fixed a bug where the sending an invalid HTTP header to the Qore::Socket::sendHTTPResponse() method could cause a crash
  • fixed bugs in system():
    • the shell was not being used to execute commands with commands where shell meta-characters were not found with a manual search which caused such commands to fail; additionally & (ampersand) characters were not recognized as shell meta-characters
    • fixed problems with signal handling in child processes on UNIXes: system() now always performs a fork(2), enables all signals, and calls execl("/bin/sh", "sh", "-c", command, 0) in the child process (on UNIX systems; on Windows, system(3) is used directly as before)
  • fixed a race condition in the DatasourcePool class when opening new datasources after a connection error in the first datasource which could cause a crash. Now the first datasource is no longer a "special" datasource used for configuration information; configuration information is contained in a separate object which serves as an internal Datasource factory
  • fixed a problem where SIGCHLD was blocked by default which caused deadlocks when spawning child processes that in turn waited on grandchild processes - now Qore no longer blocks SIGCHLD on UNIX platforms
  • fixed a bug in BinaryNode::clear() where the internal pointer was freed but not set to 0 leading to a subsequent crash when the object is destroyed; affected HTTPClient chunked reads of binary data when used with a callback
  • fixed a bug where the runtime exception location could be reported in the wrong location
  • fixed a bug where the bzip2 library can request a buffer size that could not be handled by the bzip2 library which is not handled by qore and causes a crash while decompressing certain input
  • fixed a bug handling closure-bound local variables when closures are created in the background operator expression that caused a core dump
  • fixed the precedence of the assignment operator (=); now the precedence of this operator is the same as the other assignment operators (+=, -=, *=, and /=, etc); this does not break any code, but does align Qore with other programming languages (such as C, among others) and allows for expressions such as
    a = b += 2
    to be correctly parsed
  • fixed a parse-time bug in the trim operator where the operator's return type was incorrectly returned as int instead of the type of the lvalue
  • fixed a bug initializing object members with a closure that refers to self
  • fixed bugs in the documentation and return types of:
  • fixed a bug in Qore::GetOpt::parse(softlist<auto>), Qore::GetOpt::parse2(softlist<auto>), and Qore::GetOpt::parse3(softlist<auto>) where call-by-value and copy-on-write semantics were not enforced and a shared list argument could be modified
  • fixed a bug in zoneinfo file parsing where invalid bands with no UTC offset changes against the previous band could cause invalid date/time values to be displayed by Qore for dates on the invalid transition
  • fixed a bug where imported global variables (Qore::Program::importGlobalVariable()) were added to the pending global variable list and therefore were removed if a parse exception occurred, hwoever the namespace indexes remained, which could lead to unexpected problems at runtime including a crash. Additionally the pending global variable list was not checked which could lead to a memory leak if the a single global variable name is pending, imported, and then committed to the Program object.
  • fixed memory errors managing program feature lists in the CharPtrList class by copying string memory instead of using sometimes temporary values in the list
  • fixed minor bugs with directive parsing, mostly related to error reporting
  • fixed bugs in relative date arithmetic where operands were swapped with the - operator if the first operand was a relative date/time value, additionally an operation with the - operator where the first operand is a relative date and the second operand is a absolute date is now calculated using the absolute date's epoch offset (offset in seconds and microseconds from 1970-01-01Z), and a relative date/time value is produced
  • fixed a bug normalizing the result of date arithmetic between hour and minute components of relative date/time value
  • fixed a bug where time components of absolute date/time values before the UNIX epoch were returned with invalid values
  • fixed a bug where the %exec-class directive did not check for classes with unimplemented abstract variants
  • fixed a bug where the push and unshift operators applied to a variable declared as softlist did not use the default value
  • fixed a bug where calls to Qore::HTTPClient::setConnectTimeout() had no effect (issue 323)
  • fixed several bugs with logical comparison operators and arbitrary-precision numeric values (issue 330)
  • fixed a bug where Qore::HashListIterator (and therefore <hash>::contextIterator()) would not iterate a simple hash with non-list values once but would instead silently ignore the hash (issue 336)
  • fixed a bug where a warning was not always issued when square brackets were used on unsuitable types (issue 184), internally ported the square bracket operator to the C++ QoreOperatorNode hierarchy
  • fixed a bug handling return type information for method and pseudo-method calls; uninitialized memory could be used which could cause a runtime crash (issue 364)
  • corrected the name of the modulo operator (was incorrectly referred to as the "modula" operator earlier: issue 389)
  • fixed a bug handling identifiers in parentheses used to dereference hashes or objects; the identifer is not resolved properly whereas previoulsy it was incorrectly interpreted as a string literal (issue 416)
  • fixed a bug with handling local variables in const initializers (issue 421)
  • fixed a bug where select(2) was called after EINTR without reinitializing the descriptor array argument (issue 435)
  • fixed a crashing bug on all platforms where select(2) was being called with socket descriptor values > FD_SETSIZE (issue 436)
  • fixed inconsistencies comparing relative date/time values (issue 437)
  • fixed a bug where on_exit Statements and on_error Statements statements were not being executed if an exception was raised in an earlier-executed on_exit Statements, on_error Statements, or on_success Statements statement (issue 380)
  • fixed a bug where Qore::HTTPClient::get() and Qore::HTTPClient::post() would try to retrieve a message body even if Content-Length: 0 was returned (or if no Content-Length header was returned at all) which would result in a deadlock until the server would close the connection (issue 434)
  • fixed a bug where regular expression substitution would go into an infinite loop when used with an empty pattern and the global flag (Qore::RE_Global, issue 329)
  • fixed a bug with connection handling in the SQLStatement class; an exception is now thrown if a SQLStatement object tries to execute its prepared SQL on a connection other than the original connection used to prepare the statement (issue 465)
  • fixed a bug where Qore::is_executable() would return NOTHING instead of False (as per documentation) when called with non-existent path as it's parameter (issue 470)
  • fixed precedence of logical and bitwise Operators (issue 481)
  • fixed a bug where nested lists were not parsed correctly in some cases (issue 320)
  • fixed a bug where the type of catch parameter was ignored (issue 28)
  • fixed a bug where namespace hierarchies were not indexed during parse time when added to already-committed namespaces which lead to symbol resolution errors for valid code (issue 538)
  • fixed a bug where a Socket operation attempted in another thread while a callback operation on the same socket was in progress would result in a confusing error message (issue 530)
  • fixed a bug where local variable declarations in class member initialization expressions caused a crash (issue 574)
  • fixed a bug where HTTP data in HTTP socket events was modified even though it was shared which caused data consistency problems and crashes in the worst case (issue 576)
  • fixed a bug where the `+=` operator handled NOTHING values incorrectly (issue 582)
  • fixed a bug where a non-numeric define specified on the command line could cause a crash (issue 583)
  • fixed a bug where the Qore::SQL::SQLStatement::describe() method would not grab the transation lock even when statements were implicitly executed (issue 591)
  • fixed the order of initialization of class members (issue 42)
  • fixed a bug in Qore::TimeZone::date(string) where the date returned was in the current contextual time zone and not that of the object (issue 584)
  • fixed a bug parsing windows paths in URLs with Qore::parse_url() (issue 618)
  • fixed a bug in Qore::TimeZone::constructor(string) on Windows when used with an absolute path (issue 626)
  • fixed an I/O-handling bug in the Qore::ReadOnlyFile and Qore::File classes where I/O errors in read operations were silently ignored (issue 627)
  • fixed bugs in Qore::ReadOnlyFile::readTextFile() and Qore::ReadOnlyFile::readBinaryFile() would return NOTHING instead of an empty object when reading empty files; now empty objects are returned in these cases (issue 508)
  • fixed a bug in *printf() outputs on Windows with scientific notation with floating-point values (issue 621)
  • fixed a bug where the precision of numbers during arithmetic operations was not adjusted correctly (issue 630, issue 908)
  • fixed a bug where the type of subtraction of two numbers was inferred as NOTHING during parsing (issue 636)
  • fixed a bug on Windows with Qore::Dir::create() (issue 643)
  • fixed a bug where CRLF line endings were not handled correctly by the exec-class parse directive (issue 653)
  • fixed a bug on Windows where Qore::glob() would return paths beginning with "." by default (issue 660)
  • fixed a bug on Windows where Qore::glob() would fail on "\*" or xxx "/<i></i>*" (issue 664)
  • fixed a bug on Windows where Qore::glob() would not return paths in sorted order by default (issue 665)
  • fixed a bug on Windows where the Qore::Dir class would incorrectly normalize UNC paths by stripping the leading backslash (issue 666)
  • fixed a bug where the int type restriction would accept any data type at runtime instead of throwing a RUNTIME-TYPE-ERROR exception (issue 683)
  • fixed bugs reporting the current method context with certain HTTPClient methods that would report the Socket class instead (issue 689)
  • fixed a bug handling aborted HTTP chunked transfers; now any data available for reading on a socket when a chunked transfer is aborted is read instead of having a SOCKET-SEND-ERROR thrown when the remote end closes the socket during the transfer (issue 691)
  • fixed a bug with socket handling where SSL send failures did not cause an exception to be thrown in all cases (issue 732)
  • fixed a bug on Windows where Qore::glob() returned files matched without the leading path component (issue 761)
  • fixed a bug with socket connection refused handling on Windows where connections were waiting until the timeout instead of returning an error immediately (issue 763)
  • fixed a bug where it was not possible to escape an escape character before a '$' character in a regular expression substitution target string (issue 777)
  • fixed a bug where object member references were treated as expressions returning a constant value which could cause a crash when used in an expression used to initialize a constant value at parse time (issue 817)
  • fixed a bug parsing IPv6 localhost ("::") with Qore::parse_url() (issue 822)
  • fixed a bug in Windows timezone handling caused by erroneous region names (issue 824)
  • fixed an internal memory-handling bug that caused a crash when cleaning up the qore library on FreeBSD with clang++ and possibly other platforms (issue 839)
  • fixed a bug where CALL-WITH-TYPE-ERROR exceptions were thrown based on the parse options in the caller instead of in the target when calling across a Program barrier (issue 841)
  • fixed a bug where Qore::is_writable() and Qore::is_readable() could return an incorrect value in some cases (issue 852)
  • fixed a bug where Qore::format_number() would return an invalid string when the number of decimals to be returned was 0 (issue 851)
  • fixed a bug where the delete and remove operators would incorrectly create hash keys when attempting to delete inside complex hash structures with non-existent keys (issue 855)
  • fixed a bug where duplicate global variable declarations caused a crash (issue 891)
  • fixed a memory leak in DatasourcePool initialization when the minimum connections cannot be established (issue 994)
  • fixed handling of NaN values in logical operators (issue 915)
  • fixed sort_descending_stable so that it keeps (instead of reversing) the original order of items that compare equal (issue 940)
  • fixed a bug in copy() method argument parsing; compatible type declarations were not accepted (issue 946)

Qore 0.8.11

Release Summary
Minor bugfix release for UNIX, major bugfixes for Windows

New Features in Qore

Bug Fixes in Qore

  • Windows fixes:
    • fixed TimeZone copying to use the standard name instead of the display name so that the info can be found in the registry
    • Util module fixes:
      • fixed get_random_string() on Windows
      • fixed absolute_path_windows()
    • HttpServer module fixes:
      • when binding a wildcard address with AF_UNSPEC on Windows with HttpServer::addListeners() and both IPv6 and IPv4 addresses are returned, bind both addresses since Windows doesn't direct the IPv4 requests to the wildcard-bound IPv6 listener
    • fixed file reading by always opening in binary mode
    • added support for the WSAECONNABORTED socket error
    • replaced Mime::MultiPartMessage::getRandomString() with Util::get_random_string() to make it work on Windows
  • fixed a bug in the DBI layer where calling SQLStatement::describe() would crash when called with an older module that did not implement this method
  • other fixes in the Util module (in addition to the Windows-specific fixes above):
    • fixed parse_to_qore_value() with hashes with a comma in the first key name
    • read from /dev/urandom instead of /dev/random since reads from the latter can block for long periods to fill the entropy pool
  • do not start signal thread after a fork() if signal handling is enabled, pthread_create() is not async-signal safe (on FreeBSD at least this reliably causes segfaults)

Qore 0.8.10

Release Summary
Major release with many many bugfixes and new features such as much improved HTTP and REST support (ex: chunked transfer support + new client and server classes for REST support for chunked transfers and data streaming), improved DB support (ex: new Schema module, SqlUtil improvements), and much more.

New Features in Qore

Bug Fixes in Qore

  • fixed an issue with class constant parse initialization where invalid recursive class constant definition parse exceptions could be raised and in some cases also crashes could result
  • SmtpClient module: fixed missing username and missing password errors
  • fixed a bug where a qore switch statement with no case conditions and only a default label would erroneously never have it's default code executed
  • fixed a reference leak related to exception handling with invalid arguments with Qore::Socket::setWarningQueue() and Qore::HTTPClient::setWarningQueue()
  • fixed several bugs where the parse location could be reported incorrectly for type errors regarding in-object variable references
  • fixed a bug where an error could result with Condition::wait() with timeouts > 2147483648ms
  • fixed bugs handling "bigint" and "double precision" column types with schema alignments with the PgsqlSqlUtil module
  • fixed a bug handling parse initialization of constant values requiring run-time evaluation after other parse exceptions have been raised that could cause a parse-time crash
  • fixed a bug where qore could crash on exit with certain openssl versions by calling ERR_remove_state(0) in the main thread's cleanup function
  • fixed a bug where qore could crash on exit due to user module destruction not taking into consideration user module dependencies
  • fixed a bug in schema management in SqlUtil where excessively verbose column aliases were used that caused errors when automatically updating columns with existing rows and new default values and non-null contraints with PostgreSQL databases
  • fixed a bug where a call reference to an abstract object method returned from an abstract class could be executed even though it must have been instantiated by a concrete subclass
  • fixed a bug where a valid call reference to a private object method was created within the class, then in some cases an object protection exception was raised when the call reference was called outside the class
  • fixed a bug in the RestClient module when the yaml binary module is not available
  • fixed programmatic select queries with "limit" but no "offset" in OracleSqlUtil
  • fixed a bug in Qore::Program::importFunction() where only the committed function list was checked when importing functions with a specific target namespace path
  • fixed a bug in Qore::Program::importClass() where only the committed class list was checked when importing functions with a specific target namespace path
  • fixed a bug when parsing subnamespaces into a parent namespace where the subnamespace already exists (either in the committed list or in the pending list)
  • fixed a memory and reference leak caused by recursive references when closures encapsulating an object's scope are assigned to or accessible from members of the object by making references to the object from within a closure encapsulating the object's state weak references instead of strong references
  • fixed schema information classes when the "string-numbers" driver option is enabled
  • fixed crashing bugs in Qore::get_thread_data() in certain use cases
  • fixed a bug in SqlUtil where select and row iterator operations could fail with certain select hash arguments without a "columns" entry but where column names were otherwise required
  • fixed a bug in HTTP response parsing where case-signficant comparisons where being made with certain critical header values
  • fixed a bug handling thread cancellation with the ThreadPool class
  • fixed several race conditions and potential deadlocks in ThreadPool destruction with active threads in the pool

Qore 0.8.9

Release Summary
Major release with many new features and also many bugfixes.

New Features in Qore

Bug Fixes in Qore

  • fixed a crashing bug handling access to members as default values of normal method arguments (issue 3240)
  • fixed a bug in the RestClient module where the "response-code" key of the info output hash could be missing in some cases (issue 3237)
  • fixed bugs handling object-local access in member initialization (issue 3193)
  • fixed a crashing bug when HTTP messages with duplicate Connection, Content-Encoding, Transfer-Encoding, Location, or Content-Type headers are received
  • fixed a bug parsing octal character constants in the lexer when octal digits followed the octal constant (ex: "\0441" where the "1" would cause an error)
  • allow escaping "$" character in regular expression substitution target strings, previously it was impossible to output a literal "$" + a digit, since this would be interpreted as a numbered input pattern expression
  • fixed a bug in the HTTPClient::getURL() and HTTPClient::getProxyURL() methods where the URL's path was not given with a leading "/" character
  • CsvUtil module fixes:
    • fixed "date" field handling with empty input (now maps to 1970-01-01)
    • fixed CsvDataIterator::next() when header_lines > 0 and working with empty input data
  • added support for compiling on OSX Mavericks
  • fixed an infinitely recursive call in Table::del() in SqlUtil
  • fixed a bug in v*printf() where '%' was not handled correctly in all cases
  • fixed bugs in microseconds and milliseconds() with large arguments
  • fixed a bug where a call to a call reference to a static method across a program boundary with local variables as arguments would cause a crash due to improper setting of the program context before the arguments are evaluated
  • fixed a bug in Datasource::copy() method where implicitly-set options were not carried over into the new object
  • fixed a bug in the DatasourcePool class where implicitly-opened connections would not be guaranteed to have the same server time zone setting as the initial connections (for example, could cause problems with server timezone settings if running in a program context with a different local time zone attribute)
  • fixed bugs in SqlUtil generating "create table" and "align table" SQL with DBs where unique indexes automatically create unique constraints (ex: MySQL)
  • fixed a bug in lchown() where chown() was used interally instead of lchown()
  • fixed a bug in PgsqlSqlUtil retrieving sequence values with Database::getNextSequenceValue()
  • fixed an off-by-one memory bug in Qore::date(string, string) parsing a 4-digit date mask
  • fixed memory leaks in class member and class static variable management
  • fixed memory leaks when an entire class has to be rolled back due to parse errors and the class has pending static variables
  • fixed memory leaks in constant handling with values containing call references
  • fixed a memory leak in constant destruction with parse rollbacks when the constant value was NULL
  • fixed an error in the rounding heuristic for arbitrary-precision numeric values that could produce invalid results (ex: 34.9n * 100 = 34902n)
  • enforce PO_NO_FILESYSTEM with the %include directive
  • fixed a bug managing object private data in complex inheritance cases where the same class may be inherited with virtual private data and also real private data
  • fixed a bug in socket timeout handling with select() errors
  • fixed a memory leak in handling abstract methods when multiple abstract methods with the same name but different signatures were declared in a class

Qore 0.8.8

Release Summary
Major new features and bug fixes with a particular focus on enhanced HTTP capabilities and enhanced database processing

Changes That Can Affect Backwards-Compatibility

New Features in Qore

Bug Fixes in Qore

  • fixed a bug where the ?: operator could thrown spurious exceptions when parsing because it would return the type of the initial boolean expression as the return type of the operator
  • fixed a bug where classes with unimplemented inherited abstract variants would sometimes cause runtime exceptions to be thrown when instantiated but should have instead been caught at parse time
  • fixed a parser bug where out-of-line class method definitions could not be defined in a namespace block
  • fixed a bug parsing arguments in parse_uri_query() in the HttpServer module
  • fixed several bugs where parse exceptions could show the wrong source location:
    • with type errors in function calls
    • when resolving global variables
    • in base class constructor arguments
    • for empty blocks with a missing return statement
    • when validating types used with the return statement (also associated warnings)
    • in methods calls
    • in hash value expressions
    • with redeclaring local variable return types
    • in local variable object instantiations
  • really fixed the bug thought to be fixed in 0.8.7 "where SSL errors would cause the affected thread to go into a infinite loop using 100% CPU" - this turned out to be easily reproducible on all platforms; when the SSL connection was shut down cleanly by the remote end before a response message was returned, an infinite loop would result
  • fixed a bug where it was impossible to output a single '\' character in regex substitution expressions; '\' was taken as an escape character, and '\\' was output literally, now '\\' is output as '\'
  • fixed a bug where a parse-time crash would occur when calling the copy() method for a class that does not implement an explicit copy() method
  • fixed a bug where arguments passed to a copy method were ignored; now an exception is thrown
  • fixed a bug where public members and static variables of privately-inherited classes were incorrectly treated as public attributes of the child class
  • fixed a bug where slices could be made of objects from outside the class including private members
  • fixed a bug where memberGate() methods were not being respected when taking a slice of an object
  • fixed bugs in the integer Socket::recv*() methods where a SOCKET-CLOSED exception was not thrown when the remote end closed the connection
  • fixed a bug related to out-of-order parse initialization for functions and methods which resulted in the wrong return type being returned for a method with more than 1 variant where the variant could not be matched at parse time
  • fixed a bug where a non-variable-reference member of an "our" variable declaration list would cause a crash due to passing the incorrect argument in sprintf()
  • fixed sandboxing / protection errors with inherited code; subclasses inheriting code from a parent class with different parse options would cause the child parse options to be used when running the parent class code which caused errors; now parse options are enforced properly on the block level
  • fixed the RangeIterator class; it was still abstract due to a missing Qore::RangeIterator::valid() method
  • fixed a bug where the wrong error was being returned after a connection reset (remote connection close) in sockets with integer recv*() methods which could in some cases lead to an infinite loop
  • fixed a bug where private members of a common base class were not accessible by objects of subclasses sharing the common base class
  • fixed many bugs in CsvUtil and updated the module version to 1.1
  • initialize static openssl crypto locks for multi-threaded openssl library access; without this crashes can result (for example in error queue management)
  • fixed a bug where Qore::HTTPClient::getURL() returned an invalid URL when no URL was set; now it returns NOTHING in this case
  • fixed a bug managing feature/module lists in inherited Program objects; user modules were listed in the child Program object even though user module code is not imported in child Program objects
  • fixed a bug where an invalid guard condition in critical lvalue storage code can cause unreferenced data to be returned while in a lock which can cause a crash in a multithreaded program
  • fixed a bug where references were not being written to the output variable if an exception was active when the code block exited
  • fixed a bug setting the precision for arbitrary-precision numbers with large exponents (like "1e100n")
  • implemented more strict adherence to RFC 2616 (HTTP 1.1) regarding message-body handling in requests and response message generation and parsing
  • fixed a bug with Condition::wait() on Darwin with negative timeout values where a short timeout was used instead of an indefinite wait
  • fixed bugs in the SmtpClient and MailMessage modules where mail messages were being serialized incorrectly if there were no attachments (there was no possibility to set the content transfer encoding) and also where it was not possible to set the content-type for the message body when it was sent as a part of a multipart message
  • fixed bugs handling arguments declared as type *reference (reference or nothing)
  • fixed bugs in executing code accross Program object barriers with reference arguments
  • fixed a bug with the switch statement where character encoding differences would cause strings to mismatch even if they were otherwise identical; now hard comparisons with strings allow for implicit automatic temporary character encoding conversions for the comparison
  • fixed a bug where qore failed to set the time zone region correctly when set from /etc/localtime and this file is a relative symlink rather than absolute
  • fixed a bug where substr() and <string>::substr() were returning NOTHING if the arguments could not be satisifed contrary to the documentation and the declared return type, now an empty string is returned in those cases
  • fixed bugs rounding number values between 10 and -10 (non-inclusive) for display, fixed bugs rounding number value regarding digits after the decimal point for display with Qore::NF_Scientific
  • fixed a bug in the Qore::Dir class where it was not possible to chdir to the root directory "/"
  • fixed a bug where recursive references were allowed and memory leaks would occur due to recursive references; these are now caught at runtime and a REFERENCE-ERROR exception is thrown
  • fixed a configure bug with bison >= 3
  • fixed a bug in the HttpServer module when automatically uncompressing supported content-encodings to set the resulting string's character encoding correctly
  • fixed a bug in the instanceof operator when working with objects and classes created from different source Program objects
  • fixed a bug in *printf() formatting with floating-point and number values where no digits were displayed right of the decimal point unless a specific number of digits was specified in the format string
  • fixed the return type of <bool>::typeCode(); was returning a boolean instead of Qore::NT_BOOLEAN
  • fixed a bug there NULL was evaluated as True in a boolean context rather than False
  • fixed a bug where Qore::Socket::recvBinary() would ignore the first data read
  • fixed starting listeners on UNIX domain sockets on Soalris in the HttpServer module
  • fixed a bug where number("") was being converted to @NaN@n
  • fixed return type of HTTPClient::getConnectionPath()
  • fixed several bugs with logical comparison operators and arbitrary-precision numeric values where arbitrary-precision numeric values were not being prioritized as numeric values and also in some cases were being first converted to doubles and then operated on
  • fixed a bug in the socket code where the socket close condition was not flagged with SSL connections when writes failed due to the remote end closing the connection; an error would only be raised on the following socket operation
  • fixed a mismatched delete/malloc error with time zone initialization and the localtime file

Qore 0.8.7

Release Summary
Code embedding improvements

Changes That Can Affect Backwards-Compatibility

Fixes for Code Inheritance in Program Objects
The following changes are meant to sanitize code inheritance in child Program objects to fix long-standing design bugs in code encapsulation by addressing the lack of fine-grained control over symbol visibility in inherited code.
  • public: The public keyword's usage in modules has now been expanded to provide the same functionality generically in Program objects; if classes, constants, namespaces, functions, or global variables are defined with the public keyword, then these symbols will be inherited into child Program objects as long as no parse options prohibit it.

    This change was made to give programmers complete control over which symbols are inherited in child Program objects, whereas because prior to this change, the control was very course.

  • the default behavior of Qore regarding inherting global variables and functions with user variants was changed to be consistent with namespaces, classes, and constants; that is; public symbols are inherited by default.

    The following constants were renamed:
  • builtin symbols are no longer inherited from user modules; only independent user symbols; the main change is that if a user module adds new user methods to a builtin class or new user variants to a builtin function, these changes are no longer imported into target Program objects.
File Method Changes
The following methods were updated to throw exceptions on all errors rather than a return code for I/O errors in order to avoid hard to debug conditions due to ignoring I/O errors by forgetting to check the return value on the following methods: Note that the above changes will hopefully only minimally impact backwards-compatibilty since the change is in error handling, and additionally each of the above methods could also throw an exception if called when the object was not open.

New Features in Qore

Bug Fixes in Qore

  • fixed a runtime class matching bug when identical user classes were created in different Program objects, the match could fail at runtime because the wrong APIs were being used
  • fixed a crashing bug in the map operator with a select expression when used with an AbstractIterator object for the list operand
  • fixed a bug where the generation of internal strings for abstract method signatures tries to resolve class names that are declared out of order, which incorrectly resulted in a parse exception; the fix is to use the class name in the signature before class resolution; the class is resolved in the second stage of parsing (symbol resolution) anyway, if it can't be resolved then the changes to the Program are rolled back anyway
  • a potential deadlock was fixed when calling exit() while background threads were running; it was possible for a thread to be canceled while holding a Mutex (for example) and then for another thread to deadlock trying to acquire the Mutex and therefore for the process to deadlock because pthread_mutex_lock() is not a cancellation point. The solution was to cancel all threads first, then wait half a second, then call exit()
  • fixed a bug where global variables were being evaluated with strict mathematical boolean evaluation even when %perl-bool-eval was enabled (which is the default)
  • fixed bug in Qore::parseBase64String() and Qore::parseBase64StringToString() when called with an empty string argument; in this case uninitialized memory was returned
  • fixed runtime dynamic memory leaks in the Select From List Operator (select) and Map Operator (map) operators when used with iterators
  • do thread-specific cleanup in the main thread when cleaning up/shutting down the qore library
  • added additional openssl cleanup code for thread-local data and when cleaning up the qore library
  • fixed a bug matching function/method variants at runtime
  • fixed a race condition deleting global dynamic handlers in the HttpServer module
  • fixed a bug where declaring an abstract method with parameters and then declaring a concrete reimplementation of the method in a child class with no parameters caused a parse-time crash
  • fixed a bug where trying to dynamically call a function that does not exist results in a deadlock due to an error where a mutex is not unlocked
  • fixed a bug in the Qore::Socket::sendHTTPMessage() and Qore::Socket::sendHTTPResponse() methods regarding the timeout parameter
  • fixed a bug in an socket SSL error message where the method name was printed from non-string memory (used wrong ptr for the %s format argument)
  • fixed some major crashing bugs related to reference handling; a global variable assigned a reference to a reference to a local variable would cause a crash
  • reference and *reference type fixes: an error in reference type handling allowed non-reference values to be passed to builtin code expecing references which caused a crash; the reference and *reference types would accept any value type
  • attempted to fix a non-reproducible bug seen on rhel5 in the Socket class where SSL errors would cause the affected thread to go into a infinite loop using 100% CPU

Qore 0.8.6.2

Release Summary
Iterator improvements and design fixes

Changes That Can Affect Backwards-Compatibility

Fixes for Iterator Class Design Bugs
Iterators, particular regarding the map and select operators, were implemented in a confusing and inconsistent way; even the qore documentation was incorrect, and examples were given incorrectly. The following changes will break functionality using the badly-implemented behavior of iterators before, but since the fix comes fairly soon after the introduction, hopefully this change will not cause too many problems with existing code. All users polled about the iterator changes in this release saw them as positive and desired changes to the language.

Changes in Qore

Qore 0.8.6.1

Release Summary
Major bug fixes and minor new features

Changes in Qore

  • updated the %try-module parse directive to support a variant without an exception variable for usage in Program objects where Qore::PO_NO_TOP_LEVEL_STATEMENTS is set
  • added code to raise an invalid-operation warning with the elements operator when called with a type that can never return a value with this operator
  • updated the File class's internal buffer size from 4KB to 16KB which greatly improves read performance
  • added new public APIs for the QoreNumberNode class to allow for proper de/serialization in external modules
  • Pop3Client module:
    • added the Pop3Client::logPassword() methods and masked password by default in the debug log
    • updated module to v1.1
  • Mime module:
    • declared the MultiPartMessage::getMsgAndHeaders() method abstract as originally intended
    • added MultiPartMessage::parseBody() static method
    • updated module to v1.3

Bug Fixes in Qore

  • fixed crashing bugs due to the lack of proper lvalue checks with the expression for the background operator with operators using lvalues with local variables
  • fixed rounding of arbitrary-precision numeric values for display purposes when the last significant digit is just to the right of the decimal point (ex: was displaying 10.2 as "11." for example)
  • fixed a race condition in static destruction of the library when a background thread calls exit() that could cause a segfault on exit
  • fixed a static memory leak in Program objects when constants contain code references to functions or static methods
  • fixed a bug parsing user modules; the Program context was not set properly which could lead to a crash when parsing user modules loaded from the command-line or to incorrect parse options when loaded from user Program code
  • fixed a bug where the invalid-operation warning with the keys operator was not being triggered in common cases that should have triggered the warning
  • MailMessage module:
    • fixed recognizing mime messages with additional text after the version number (ex: "Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))")
    • fixed a bug setting the content-type of message parts (this fix is now in the Mime in the MultiPartMessage::getMsgAndHeaders() method
    • fixed multipart message parsing by using MultiPartMessage::parseBody() in the Mime module; now also parts with subparts are parsed correctly as well
    • fixed a bug where the sender and from values were not being set properly when parsing email messages
    • updated module to v1.0.3

Qore 0.8.6

Release Summary
Major new features and a few bug fixes

Changes That Can Affect Backwards-Compatibility

Perl-Style Boolean Evaluation
Qore's default boolean evaluation mode was changed from strict mathematical to a more intuitive perl- (and Python-) like style. This change was implemented to address one of the oldest design bugs in Qore: strict mathematical boolean evaluation. See %perl-bool-eval for a description of the new default boolean evaluation mode.

To get the old strict mathematical boolean evaluation, use the %strict-bool-eval parse option.

An example of the change; now the following if statement block will be executed as the if expression is now evaluated as True:
string str = "hello";
if (str)
printf("Qore says hello\n");
Previously (i.e. with %strict-bool-eval) the if expression above would be evaluated as False because the string value was converted to an integer 0, however as of Qore 0.8.6 (with the default perl-bool-eval) it is True since the string is not empty; empty strings and string value "0" are evaluated as False.

Perhaps counterintuitively (and the reason this was changed to be the default in qore), the chance for regression errors in qore code is very small, because for all cases where the old logic could be applied (meaning excluding cases where the result was always False due to the data types or values being evaluated), the results are the same with the new logic, except for one case; the case where a string has more than one character and begins with a zero (ex: "00"). In this case, the old logic would always return False, because the value was first converted to an integer 0, whereas the new logic will return True. Note that in the case of a string with a single "0", both the old and new boolean logic returns False.

Basically with this option set, qore's boolean evaluation becomes like perl's and Python's, whereas any expression that has the following values is False: NOTHING, string "0" and empty strings, integer, float, and number 0 (zero), absolute date 1970-01-01Z (ie the start of the epoch with an offset of 0), relative date 0s (or any relative date with a 0 duration), NULL, empty binary objects, empty hashes, and empty lists. All other values are True.
Note
also affects the boolean(any) function
Changes in the Socket Class
The Socket class was enhanced to support timeouts with non-blocking I/O on all send operations; many Socket methods that send data were originally implemented to return an error code on error, however they would also throw exceptions if the socket were not open, so the error handling was inconsistent (exceptions versus return codes).

Additionally it was not possible to get error information at all for SSL errors if the socket was connected with SSL, which, according to Qore's socket design, should be transparent for the programmer.

For these reasons the implementation was deemed inconsistent and unintuitive; the change was to add optional timeout parameters to all send methods and to allow the methods to throw exceptions (instead of simply returning -1 and not being able to determine the cause of the error in many cases).

The following methods were updated to accept optional timeout parameters and throw exceptions on all errors rather than a return code for I/O errors:
New Abstract Method in AbstractIterator
The following abstract method was added:
  • Qore::AbstractIterator::valid() was added (with concrete implementations in all iterator classes derived from this base class delivered with Qore); this method tells if the object is currently pointing to a valid iterator.

    For any user classes inherting AbstractIterator directly (as opposed to another concrete iterator class in Qore, where the method has already been added), a concrete implementation of this method will have to be added as well or that class will become abstract with this release of Qore.

New Features in Qore

Arbitrary-Precision Numeric Support
Qore now uses the MPFR and GMP libraries to provide arbitrary-precision numeric support. This type can be used for high-precision mathematics or for storing NUMERIC (ie DECIMAL or NUMBER) column values when retrieved from databases by Qore DBI drivers that support the new capability DBI_CAP_HAS_NUMBER_SUPPORT (previously these values would be retrieved as Qore strings in order to avoid information loss).

For more information, see the new number type, number, and <number>
New CsvUtil Module
The CsvUtil module implements the CsvFileIterator class that allows for easy parsing of csv-like text files
%try-module Parse Directive to Handle Module Load Errors at Parse Time
The new %try-module parse directive allows for module load errors to be handled at parse time; ex:
%try-module($ex) some-module > 1.0
printf("error loading module %y: %s: %s\n", ex.arg, ex.err, ex.desc);
exit(1);
%endtry
Abstract Class Hierarchy Improvement
As of this version of qore, concrete implementations of abstract methods no longer have to have exactly the same return type as the abstract method; it is now sufficient that the return type in the concrete method meets a compatibility test with the return type of the abstract method in the parent class.

For example the following is now valid (and MyConcreteClass is not abstract, whereas previously because the return types in the child class were not exact, MyConcreteClass would be considered abstract by qore):
class MyAbstractClass {
abstract any doSomething();
abstract *string getString();
}
class MyConcreteClass inherits MyAbstractClass {
int doSomething() {
return 1;
}
string getString() {
return "hello";
}
}
DBI Improvements
Three new DBI capabilities were implemented, including a new option API as follows:
  • DBI_CAP_HAS_NUMBER_SUPPORT: DBI drivers declaring this capability can accept number values and can also return number values, if a DBI driver does not declare this capability, then number values sent for binding by value are automatically converted to float values before being sent to the driver
  • DBI_CAP_HAS_OPTION_SUPPORT: this indicates that the driver supports the new option API, allowing options to be set on each connection. See the following for more information:
  • DBI_CAP_SERVER_TIME_ZONE: indicates that the DBI driver will convert any bound date/time values to the server's time zone before binding and also will tag date/time values retrieved from the server with the server's time zone. This capability also implies that the driver supports the new "timezone" option.
Socket Improvements
The Socket class was updated to support non-blocking I/O on all send methods; the following methods were updated to accept optional timeout parameters: The following methods were enhanced to provide better error information when throwing exceptions:
Iterator Improvements
The following improvements were made in qore to support more flexible and ubiquitous iterators:
Text File Parsing Enhancements
The following improvements were made in qore to support more flexible file parsing:
Other Improvements and Changes

Bug Fixes in Qore

  • fixed a bug in the map operator with a select expression when the list operand is NOTHING; it was returning a list with one NOTHING element instead of NOTHING
  • applied a patch by Reini Urban to allow for multi-arch builds on Debian
  • fixed bugs calculating the byte offset for string searches in the c++ QoreString::index() and QoreString::rindex() functions when the offset is negative and the strings have a multi-byte character encoding (such as UTF-8)
  • fixed a bug where calling an abstract method from a class where the abstract method is implemented was causing a parse error to be thrown
  • fixed a bug where the wrong source code location was displayed when raising a parse exception in operator expression parse initialization for some operators
  • fixed bugs in regexes in the HttpServer::addListeners() and HttpServer::addListenersWithHandler() methods (HttpServer module version updated to 0.3.5)
  • fixed bugs handling non-blocking reads in the Socket class; the timeout setting was only enforced for the first read; subsequent reads were made as blocking reads
  • fixed a bug in the Socket class when the SSL session requires renegotiation during non-blocking I/O
  • File::constructor() now throws an exception if called with a tty target and %no-terminal-io is set
  • fixed a bug in split with quote (<string>::split(string, string, bool) and Qore::split(string, string, string, bool)) if the separator pattern was not found and the single field was not quoted either
  • fixed a bug handling nested %ifdef and %ifndef blocks with %else in the inside block
  • fixed a crashing due to the failure to clear the "PF_TOP_LEVEL" flag when initializing statements, this could cause temporary variables in a statement to be marked as the start of the global thread-local variable list, and then after such variables are deleted, then a crash happens when trying to access the global thread-local variable list
  • fixed a crashing bug at parse time merging function lists in namespaces declared multiple times
  • fixed a bug in executing user module init() closures
  • fixed a bug where the qore library could crash when destroying a Program object due to a race condition in removing signal handlers managed by the Program object; the Program calls the signal handler manager to remove the signals, but the signals can be removed concurrently to the request while the Program object is iterating the signal set (ie it is modified while being iterated), which causes a crash
  • added code to detect when the same namespace is declared both with and without the public keyword when defining user modules which can result in entire namespaces being silently not exported (and can be difficult to debug); now a parse exception is thrown if this happens while parsing a user module
  • added code tags to File methods without side effects
  • made many minor documentation fixes

Qore 0.8.5.1

Release Summary
Bugfix release

Bug Fixes in Qore

  • fixed a race condition accessing global and closure-bound thread-local variables in multithreaded contexts
  • fixed a bug in transaction management with the DatasourcePool class when used with the SQLStatement class
  • fixed an error in the MailMessage user module where mail headers requiring encoding were not encoded and those not requiring encoding were encoded with Q encoding
  • fixed an error in the Mime user module where "_" characters in q-encoded headers were not encoded correctly

Qore 0.8.5

Release Summary
Major new features and a few bug fixes

New Features in Qore

Abstract Methods and Interfaces
Qore now supports the abstract keyword when declaring methods; an abstract method has no implementation and must be implemented in child classes with the same signature for the child class to be instantiated.

Classes with abstract methods define interfaces; a concrete implementation of the interface is a class that inherits the class with abstract methods and implements all the abstract methods.

Abstract methods are defined with the following syntax:
class MyAbstractInterface {
abstract string doSomething(int param);
abstract bool checkSomething(string arg);
}
The following abstract classes now exist in Qore: The following new iterator classes have been added to Qore: Classes inheriting AbstractIterator have special support so that objects can be easily iterated in the following list operators:
Universal References
All restrictions on references have been removed from Qore; references to local variables may now be passed to the background operator and passed as arguments to closures.

Basically when a reference is taken of a local variable that could result in the local variable being accessed in a multi-threaded context, the variable is treated as a closure-bound local variable in the sense that it's lifetime is reference-counted, and all accesses are wrapped in a dedicated mutual-exclusion lock to ensure thread safety.
Pop3Client Module
A Pop3Client module has been added providing an API for communicating with POP3 servers and retrieving email messages.

The module uses functionality provided by the new MailMessage module to represent email messages (and attachment data) downloaded from the server.
MailMessage Module
The MailMessage module provides common functionality to the Pop3Client and SmtpClient modules to represent email messages for receiving and sending, respectively. This module was created mostly from functionality removed from the SmtpClient and enhanced to provide support for reading email messages in the new Pop3Client module.
SmtpClient Module Changes
The Message and Attachment classes were removed from the SmtpClient module to the MailMessage module. Backwards-compatible definitions for the Message and Attachment classes are provided in the SmtpClient module to rexport the removed functionality for backwards compatibility.
Other Minor Improvements and Changes

Bug Fixes in Qore

  • fixed format_date() output for "MON" and "DAY", etc
  • fixed a memory leak in the parser related to parse exception handling with namespace members
  • fixed an invalid assert() in module handling when an error occurs loading the module (only affected debug builds)
  • tagged digest and crypto functions internally as RET_VALUE_ONLY
  • do not kill TID 1 (the initial / main thread) when calling exit() in background threads as a crash can result with some 3rd party libraries that spawn their own threads on some platforms (observed on Darwin & Solaris 10 at least)
  • fixed a memory bug in the new builtin function API used by modules built with qpp
  • fixed memory bugs in the type system where uninitialized type pointers could be used causing a crash
  • fixed a memory bug in handling "or nothing" types where a non-null pointer would be assumed to be a pointer to the type, however it could actually be a pointer to the NOTHING object, the fix was to ensure that any NOTHING objects in argument lists would be substituted with a null pointer
  • fixed a bug in parse-time variant matching where an argument with parse-time type "object" would be matched as a perfect match to any parameter with any class restriction; this would cause run-time type errors if another valid class was passed that matched another variant of the method or function
  • fixed a build bug that caused qore to be built twice

Qore 0.8.4

Release Summary
Major new features and changes that can affect backwards-compatibility, plus 40 bug fixes

Changes That Can Affect Backwards-Compatibility

Namespace Changes
Qore's internal namespace handling was nearly completely rewritten for Qore 0.8.4. This is because the old code was inefficient and applied namespaces inconsistently to Program objects.

The main change that can cause backwards-compatibility issues is that now functions are full namespace members. If no namespace is explicitly given in a function definition, the function is a member of the unnamed root namespace.

Also the distinction between builtin and user functions was removed. Internally, there is only one kind of function object, which can contain both builtin and user function variants (overloaded variants of the same function with the same name but different arguments).

All Qore builtin functions were moved to the Qore namespace.

Other namespace changes:
  • loading namespaces provided by builtin modules into a Program object is now an atomic operation that may fail, if, for example, objects have already been defined in the target Program with the same name as objects provided by the builtin module. Previously this could cause undefined behavior.
  • namespace lookups are now truly breadth-first as documented; previously the algorithm was depth-first (contrary to the documentation)
  • namespace lookups are now done (both at parse time and runtime) with the help of symbol lookup tables for fast lookups; tables are maintained for both committed and temporary uncomitted parse symbols; this leads to up to 3x faster parsing for Qore code
  • global variables are also now full namespace members, however this does not cause problems with backwards-compatibility

New Features in Qore

User Modules
It is now possible to develop user modules in Qore; several user modules are now included in the Qore distribution, forming Qore-language components of Qore's runtime library.

User modules delivered with Qore 0.8.4:
  • HttpServer: a multi-threaded HTTP server implementation
  • SmtpClient: an SMTP client library
  • TelnetClient: a TELNET client implementation
  • Mime: a set of MIME definitions and functions for manipulating MIME data
There are also new example programs for the above modules in the examples/ directory.

User modules are subject to Qore's functional restriction framework.
Namespace Changes
As listed above:
  • global variables and functions are now full namespace members
  • all builtin functions are now in the Qore namespace
  • real depth-first searches are used for namespace symbols
  • symbols are resolved first in the current namespace when parsing declarations/code in a namespace
The final Keyword
Classes and methods can now be declared "final" to prevent subclassing or overriding in a subclass
Pseudo Methods
Pseudo-methods are class methods that can be implemented on any value; they are also part of class hierarchy. The methods that can be executed on the value depend on the value's type, and all "pseudo-classes" inherit methods from a common base class.

For example:
"string".strlen()
<abf05da3>.size()
500.typeCode()
Are examples of pseudo-methods on literal values.

Some expensive operations such as getting the first or last key (or value) of a hash are now cheap using pseudo-methods, for example:
hash.firstKey()
hash.lastValue()
New Doxygen-Based Documentation
The Qore reference documentation is now generated by Doxygen, and is generated directly from the Qore sources. In fact, a new preprocessor known as "qpp" was developed for Qore 0.8.4 to facilitate and enforce doxygen documentation on Qore's runtime library (as well as abstract the relatively complex APIs used to bind C++ code to the Qore runtime library from the C++ programmer).

The documentation is more comprehensive, and corresponds much closer to the actual internal implementation since the documentation is now also contained in and directly generated from the internal C++ implementation of Qore.

For example, there is the <value>::val() method. This method is implemented in the base pseudo class and is reimplemented in other pseudo-classes for other runtime data types as necessary. This method returns True if the value has a value in the same sense as Perl's boolean context evaluation. For example, if the value is a hash with no keys, it returns False; if it is a hash with keys, it returns True; if it is an empty string, it returns False; if it is a non-empty string, it returns True, etc.
LValue Handling Changes
lvalue handling was rewritten as the old implementation was ugly and subject to deadlocks (in rare corner cases).

Furthermore, medium-term, an architectural goal of Qore is to store all ints, floats, and bools internally as the basic C++ type instead of using a class wrapper for each value, which needs dynamic allocation and destruction, which takes up more memory and negatively affects execution speed.

With Qore 0.8.4, all local and global variables are stored using optimized C++ types when declared with the appropriate type restrictions; for example:
int i0;
our int i1;
These declares local and global variables that can only be assigned integer values; in Qore 0.8.4 the value internally will be stored as an "int64" value (and not a dynamically-allocated QoreBigIntNode object).

The same holds for: Note that the optimized lvalue handling has not yet been applied to all lvalues, in particular non-static object members with declared types are not yet implemented with optimized storage; to do this requires a rewrite of Qore's API and ABI (will happen in the next major release of Qore).

This change leads to improved integer and floating-point performance and a smaller runtime memory footprint.
Runtime Optimizations
In addition to the up to 3x faster parsing (as decribed in the namespace changes above), Qore 0.8.4 contains many runtime optimizations designed to reduce the number of dynamic memory allocations performed at runtime.

The optimizations included in this version of Qore are only a half-measure compared to future changes that will necessitate a new binary Qore API.
Per-Thread Initialization
the new set_thread_init() function allows a call reference or closure to be set which will be automatically executed when new threads are started (or a new thread accesses a Program object) which can be used to transparently initialize thread-local data.
More Control Over Thread Resource Exceptions
new functions: Allow for only thread resouces created after a certain point to be processed (for example only thread resources left after some embedded code was called)
New Socket Methods
new methods: Allow upgrading an already-existing socket connection to SSL
Better Socket Error Messages
More information has been added to socket exceptions to provide better feedback when errors occur.
New Socket Event Fields
Support For Blocking Writes in the Queue Class
Queue objects can now be used as a blocking message channel (similar to a Go channel); if a maximum size is given to the Queue constructor, then trying to write data to the Queue when it is full will block until the Queue's size goes below the maximum size; optional timeout parameters have been added to Queue methods that write to the Queue.
New Queue::clear() Method
Does just what you think it does :)
date(string, string) Improvement
added the possibility to specify microseconds when parsing dates against a mask with the date() function
New Support For ++ And – Operators With Floating-Point Lvalues
previously this would either convert the lvalue to an int or throw an exception if the lvalue could not be converted to an int due to type restrictions
Class Recognition/Compatibility Between Program Objects
The problem is that a user class created from the same source code in two different Program objects would be recognized as a different class with parameter and variable type restrictions - ie you could not declare a variable or parameter with a class type restrictions and assign it an object created from the same class source code but created in another Program object.

This problem is analogous to a similar problem with java in that classes built from the same source but from different classloaders are also recognized as different classes.

In Qore 0.8.4 a class signature is created of all public and private objects, and an SHA1 hash is maintained of the class signature, and if the class names and signatures match, then the classes are assumed to be identical, even if they have different internal class IDs (because they were created in different Program objects, for example).
New TimeZone::date(string) Method
to support creating arbitrary dates in a given TimeZone
New GetOpt::parse3() method
This method will display any errors on stderr and exit the program (which is the most typical way of handling command line errors anyway)
+= Operator Optimization For object += hash
this operation is faster in this release
New Parse Option PO_NO_MODULES
Using this option disables module loading
New Parse Option PO_NO_EMBEDDED_LOGIC
Using this option disables all dynamic parsing
New Parse Directives
New Context Functions
SOCKET-HTTP-ERROR Exception Enhancement
The invalid header info received is reported in the exception's "arg" key
Improved Parse Error Messages
Improved some parse error messages dealing with namespace and class declaration errors
Added NT_CLOSURE Constant
type code for runtime closure values

Bug Fixes in Qore

  • fixed a race condition with Program objects when a signal handler is left active and the Program terminates
  • fixed a bug in the File class where the encoding given in the constructor was ignored; if no encoding was given in the File::open*() method then the File's encoding would always be set to the default encoding, now it's set to the encoding given in the constructor (as documented)
  • runtime checks have been implemented so that references to local variables cannot be passed to a closure; this would cause a runtime crash
  • a fix has been made to the delete and remove operators; lists will not be extended when trying to remove/delete list elements that do not exist
  • fixed some bugs showing the error location with bugs in the second stage of parsing (symbol resolution)
  • apply type filters to blocks with a designated return type but no return statement
  • fixed crashing bugs on some 32bit platforms where size_t was assumed to be 64 bits
  • fixed a crashing bug parsing invalid %requires directives in the scanner
  • fixed a bug in usleep() with relative date/time values (added a new usleep() variant to support this)
  • fixed a typo in the command-line help for the qore binary with unknown parse options
  • fixed HAVE_SIGNAL_HANDLING to be False if signal handling is disabled on platforms where signal handling is otherwise available
  • fixed a scanner bug parsing out of line class definitions with a root-justified namespace path (ex: "class ::X::ClassName ...")
  • merging code from binary modules at parse time and at runtime is now transaction-safe (before it would cause memory errors and/or a crash), now if errors are detected then an exception is raised and changes are not applied.
  • fixed a crashing bug in the C++ API function QoreHashNode::setKeyValue() when the value is 0 and an exception occurs or is already active before the call is made
  • fixed a bug in date parsing with a format string - off by one with integer months - added a regression test for this case
  • fixed a memory error with the rethrow statement in enclosing but nested try-catch blocks
  • fixed a crashing bug where qore would try to instantiate a class for a type that did not represent a class (ex: "int i();")
  • fixed a memory leak in the softlist and *softlist type implementation
  • make sure and raise a SOCKET-CLOSED error when reading a HTTP header if no data is received
  • make sure and convert encodings with index() and rindex() functions if the encodings don't match
  • build fix: only use a lib64 directory if the directory exists already
  • raise a parse exception in the scanner if a numeric overflow occurs in literal integer values
  • fixed a bug in AbstractSmartLock::lockTID()
  • fixed a major crashing error in the C++ API function QoreStringNode::createAndConvertEncoding(); this function is used by the xml module when parsing XML-RPC sent in a non-UTF-8 character encoding
  • fixed Qore::File::getchar() to always retrieve 1 character (even for multi-byte character encodings)
  • fixed string evaluation in a boolean context to return True with floating-point numbers between -1.0 and 1.0 exclusive
  • printf formatting fix: output YAML-style "null" for NOTHING with %y
  • scanner fix: accept "\r" as whitespace to allow better parsing of sources with Windows EOL markers
  • fixed parse-time type processing/checks for the keys, + and * operators
  • foreach statement fix: unconditionally evaluate the hash when iterating as otherwise it could change during iteration which could cause a crash
  • fixed another parse-time variant matching bug where the variant-matching algorithm was too aggressive and excluded possible matches at parse time which could result in a false parse-time definitive match even though a better match could be available at runtime
  • fixed a static memory leak when signal handlers are left registered when the qore library terminates
  • fixed static memory leaks and 1 dynamic memory leak in strmul()
  • fixed a crashing bug in handling recursive constant references
  • fixed a bug in the C++ API function HashIterator::deleteKey() when the node's value is NULL
  • fixed time zone/DST calculations for time zone regions with DST with dates before the epoch but after the last DST transition before the epoch
  • fixed a memory error where invalid source expressions referenced in a regular expression substitution expression would cause a crash (ex:
    str =~ s/public (name)/$2/g 
  • fixed a memory error in regular expression substitution where the unconverted string (if not given in UTF-8 encoding) was used when copying source expressions to the target string
  • fixed a bug where a recursive class inheritance tree would cause a crash
  • fixed a bug where a static class method could not access private members of the class
Qore::printf
string printf(string fmt,...)
Outputs the string passed to standard output, using the first argument as a format string; does not e...
Qore::strlen
int strlen(softstring str)
Returns the length in bytes of the string argument.