2,951
edits
m (8 revisions imported: Migrate from miraheze) |
mNo edit summary |
||
Line 8: | Line 8: | ||
APL's string notation is very simple and includes only one [[wikipedia:Escape sequence|escape]]: two adjacent single quotes within a string stand for one single quote character rather than ending the string and starting a new one. To [[strand]] strings together, put spaces between them. A newline character within a string produces an error. To produce newlines or other non-printing characters which would be inconvenient to include in the source, use an alternative [[character]] creation mechanism, such as [[Unicode Convert]] (<source lang=apl inline>⎕UCS</source>). | APL's string notation is very simple and includes only one [[wikipedia:Escape sequence|escape]]: two adjacent single quotes within a string stand for one single quote character rather than ending the string and starting a new one. To [[strand]] strings together, put spaces between them. A newline character within a string produces an error. To produce newlines or other non-printing characters which would be inconvenient to include in the source, use an alternative [[character]] creation mechanism, such as [[Unicode Convert]] (<source lang=apl inline>⎕UCS</source>). | ||
Some users of [[Nested array model|nested]] APLs have proposed a dedicated string datatype to allow strings to be manipulated as a single entity, and in particular, to allow them to be compared with [[scalar function]]s. In [[Flat array model|flat]] APLs these problems are not felt so strongly because [[box]]ed arrays behave more like a simple datatype. | Some users of [[Nested array model|nested]] APLs have proposed a dedicated [[string datatype]] to allow strings to be manipulated as a single entity, and in particular, to allow them to be compared with [[scalar function]]s. In [[Flat array model|flat]] APLs these problems are not felt so strongly because [[box]]ed arrays behave more like a simple datatype. | ||
== External links == | == External links == |