Topics related to the use of Oberon language features
-
augustk
- Posts: 54
- Joined: Mon Sep 05, 2011 5:21 pm
- Location: Sweden
Post
by augustk » Mon Oct 03, 2011 8:37 pm
i would vote for the introduction of a predefined procedure for (compile-time) string concatenation. This function procedure (with a variable number of parameters) could be named UNION. With this minimal addition to the language all strings can be represented. Like kevinhely, I would also like to see the reintroduction of single quotes. The constant declaration in my previous example can then be written like this:
Code: Select all
path* = UNION('"', "C:\temp\", '"')
-
kevinhely
- Posts: 29
- Joined: Wed May 18, 2011 3:35 am
Post
by kevinhely » Wed Oct 05, 2011 2:00 pm
With single quotes, your code can be

-
augustk
- Posts: 54
- Joined: Mon Sep 05, 2011 5:21 pm
- Location: Sweden
Post
by augustk » Wed Oct 05, 2011 6:48 pm
OK, you got me, but I am sure you get my point. With the compile-time concatenation procedure all strings can be represented, just as all representable booleans, numbers and sets can be denoted by constant literals. It is a matter of completeness.
-
cfbsoftware
- Site Admin
- Posts: 534
- Joined: Fri Dec 31, 2010 12:30 pm
-
Contact:
Post
by cfbsoftware » Wed Dec 24, 2014 5:27 am
augustk wrote:It is unfortunate that character array variables cannot be exported.
Export of record and array variables in read-only mode was implemented in v5.1 of Astrobe following the changes in revision Rev 1.10.2013 / 10.03.2014 of the Oberon Language Report.