Revision History | ||
---|---|---|
Revision V7.1-005 | 18 September 2024 |
|
Revision V7.1-004 | 27 June 2024 |
|
Revision V7.1-003 | 23 November 2023 |
|
Revision V7.1-001 | 26 June 2023 |
|
Revision V7.1-000 | 04 April 2023 |
|
Revision V7.0-005 | 02 December 2022 |
|
Revision V7.0-004 | 20 September 2022 |
|
Revision V7.0-003 | 24 June 2022 |
|
Revision V7.0-002 | 23 March 2022 |
|
Revision V7.0-001 | 24 November 2021 |
|
Revision V6.3-012 | 08 April 2020 |
|
Revision V6.3-010 | 31 October 2019 |
|
Revision V6.3-007 | 04 February 2019 |
|
Revision V6.3-006 | 26 October 2018 |
|
Revision V6.3-005 | 29 June 2018 |
|
Revision V6.3-004 | 23 March 2018 |
|
Revision V6.3-003 | 12 December 2017 |
|
Revision V6.3-001 | 20 March 2017 |
|
Revision V6.2-001 | 27 February 2015 |
|
Revision V6.1-000 | 28 August 2014 |
|
Revision V6.0-003 | 24 February 2014 |
|
Revision V6.0-001 | 21 March 2013 |
|
Table of Contents
This chapter describes M language Intrinsic Functions implemented in GT.M. Traditional string processing functions have parallel functions that start with the letter "z". The parallel functions extend the byte-oriented functionality of their counterparts to UTF-8 mode. They are helpful when applications need to process binary data including blobs, binary byte streams, bit-masks, and so on.
Other functions that start with the letter "z" and do not have counterparts implement new functionality and are GT.M additions to the ANSI standard Intrinsic Functions. The M standard specifies standard abbreviations for Intrinsic Functions and rejects any non-standard abbreviations.
M Intrinsic Functions start with a single dollar sign ($) and have one or more arguments enclosed in parentheses () and separated by commas (,). These functions provide expression results by performing actions that are impossible or difficult to perform using M commands.