|
Qore Programming Language Reference Manual
0.8.11.1
|
|
Qore Programming Language Reference Manual
0.8.11.1
|
"filename" key when run in a Program context with Qore::PO_NO_EXTERNAL_INFO set"forupdate" select option"write-headers" option to CsvUtil::AbstractCsvWriter and subclasses to enable headers to be suppressed"optimal-quotes" option to CsvUtil::AbstractCsvWriter and subclasses to enable more efficient csv output (now the default)"columns" entry but where column names were otherwise requiredCsvAbstractIterator: base abstract iterator class for iterating line-based CSV dataCsvDataIterator: iterator class allowing for CSV string data to be processed line by line on a record basisAbstractCsvWriter: a base class for new CSV writer implementationsCsvFileWriter: CSV file writer classCsvStringWriter: CSV in memory writer class"headers" in the constructor if "fields" are set; headers are assumed to be the field labels in the same orderContent-Type request header when sending stringsAccept header correctly in requests (previously only indicated yaml ("text/x-yaml") as an acceptible response encoding)OPTIONS method"Bad Request" error if an unsupported HTTP method is used in a REST CallUpsertInsertOnly upsert strategy to SqlUtil"application/wsdl+xml")"xls" and "xlst" extensions to MimeTypeXmlConnection, Content-Encoding, Transfer-Encoding, Location, or Content-Type headers is received"\0441" where the "1" would cause an error)"date" field handling with empty input (now maps to 1970-01-01)'%' was not handled correctly in all cases"name" and optionally "link" keys for symbolic links; additionally symbolic links are now followed and files and directories are differentiated based on their targets when processing symbolic linksg specifier to extract all occurrences of the pattern(s) in a string; also regex_extract() and <string>::regexExtract(string, int) now accept Qore::RE_Global to extract all occurrences of the pattern(s) in a string"%y" format specifier now produces YAML-like output for the binary valueSOCKET-CLOSED exception was not thrown when the remote end closed the connection"/" REFERENCE-ERROR exception is thrownPO_INHERIT_USER_FUNC_VARIANTS is now: PO_NO_INHERIT_USER_FUNC_VARIANTSPO_INHERIT_GLOBAL_VARS is now: PO_NO_INHERIT_GLOBAL_VARSsource and offset information is present"source" and "offset" added for parse and runtime exceptions to allow for error-reporting to display information about files where sections of a source file are parsed; this allows both the label and line offset in the label and the file name and absolute file line position to be reported in exception information"us" for microseconds (see Date Formatting Codes)"STARTTLS" command when connecting to an ESMTP server; this way the class will automatically upgrade the connection to a secure TLS/SSL connection if the server supports it"esmtptls://user@password:smtp.example.com")"smtps" scheme with a default port of 465%s format argument)"Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))")if expression is now evaluated as True: 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."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."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. 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).MyConcreteClass is not abstract, whereas previously because the return types in the child class were not exact, MyConcreteClass would be considered abstract by qore): "timezone" option."key" and "value", allowing for more convenient iteration with constructions that only use getValue() methods (such as the foreach statement); to accommodate this, two new methods were added to the HashIterator base class:
"\n", "\r", or "\r\n"; the last one only if the underlying file is not a TTY in order to avoid stalling I/O on an interactive TTY)"A" and "a", (hexadecimal floating-point output) "G", "g", (compact floating-point output) "F", (non-scientific floating-point output) and "E" and "e" (scientific/exponential floating-point output) format arguments for floats and numbers (new arbitrary-precision number type values); see String Formatting"number" instead of "string" (see also sql_binding)"_" characters in q-encoded headers were not encoded correctlyQOREADDRINFO-GETINFO-ERROR exception description by adding information about the arguments passed"host" output key for indicating that the ipv6 protocol be used"MON" and "DAY", etc"type" and "typename" keys to the EVENT_HOSTNAME_RESOLVED event"type", "typename", and "address" keys to the EVENT_CONNECTING event"arg" key"class ::X::ClassName ...")"my int $i();")SOCKET-CLOSED error when reading a HTTP header if no data is received"null" for NOTHING with %y"\r" as whitespace to allow better parsing of sources with Windows EOL markersstr =~ s/public (name)/$2/g