Useful API Functions - Versionsgeschichte

Sv: Änderung übernommen aus altem Wiki von cg, 16.2.26

2026-02-23T10:43:05Z

Änderung übernommen aus altem Wiki von cg, 16.2.26

← Nächstältere Version		Version vom 23. Februar 2026, 10:43 Uhr
Zeile 15:		Zeile 15:
	== [[Collection API Functions \| Collection]] ==		== [[Collection API Functions \| Collection]] ==

	Collection is an abstract class, serving as a superclass for a number of useful concrete classes (such as Set, Dictionary, Tree, SortedCollection, String etc.)		Collection is an abstract class, serving as a superclass for a number of useful concrete classes (such as Array, ByteArray, Set, Dictionary, Tree, SortedCollection, String etc.)
	It is useful to get a feeling of the set of operations provided there (there are a lot!), so you should not have to reinvent the wheel.		It is useful to get a feeling of the set of operations provided there (there are a lot!), so you should not have to reinvent the wheel.

Zeile 23:		Zeile 23:
	== [[Filename API Functions \| Filename]] ==		== [[Filename API Functions \| Filename]] ==

	Although strings could be used to represent file names and ~~pathes~~, expecco uses instances of a specialized class called "''Filename''" to represent those. Filename instances know about any details of the underlying operating system (such as the directory separator, any naming restrictions etc.) and also provide a number of useful functions for file and directory access. Filename provides a portable representation, so that code can run on both Windows and Unix unchanged (that is: use "/" in filenames when possible. On a Windows machine, these will be replaced internally by "\" characters).		Although strings could be used to represent file names and paths, expecco uses instances of a specialized class called "''Filename''" to represent those. Filename instances know about any details of the underlying operating system (such as the directory separator, any naming restrictions etc.) and also provide a number of useful functions for file and directory access. Filename provides a portable representation, so that code can run on both Windows and Unix unchanged (that is: use "/" in filenames when possible. On a Windows machine, these will be replaced internally by "\" characters).

			Of course, there are still many differences between the systems, the most obvius being different pathes. For that, the Filiename class provides a number of accessors, for example to get the path to the home directory, the path to the temp folder etc. Do not hardcode any pathnames into your code or testSuite; instead either use the above mentioned accessors, or place the pathes into a global variable, so they can be both easily found and also easily overwritten by eg. the command line or a config file.

	Read more: [[Filename_API_Functions\|Filename API Functions]]<br>		Read more: [[Filename_API_Functions\|Filename API Functions]]<br>
Zeile 49:		Zeile 51:

	== [[Date & Time]] ==		== [[Date & Time]] ==
	Expecco provides a number of time related support classes: TimeDuration, Time, Date and Timestamp (aka. ''TimeAndDate'') for local, UTC and ~~timezone~~ specific. Although timestamps support picosecond precision, current operating systems will only provide milli or microsecond resolution timestamps. However finer resolution values may come from exact measurement devices or be computed in technical/physical processes.		Expecco provides a number of time related support classes: TimeDuration, Time, Date and Timestamp (aka. ''TimeAndDate'') for local, UTC and time zone specific. Although timestamps support picosecond precision, current operating systems will only provide milli- or microsecond resolution timestamps. However finer resolution values may come from exact measurement devices or be computed in technical/physical processes.

	Read more: [[Date_and_Time_API_Functions\|Date and Time API Functions]]<br>		Read more: [[Date_and_Time_API_Functions\|Date and Time API Functions]]<br>

Cg: /* Physical Values */

2025-06-05T09:14:10Z

Physical Values

← Nächstältere Version		Version vom 5. Juni 2025, 09:14 Uhr
Zeile 55:		Zeile 55:

	== [[PhysicalValues/en\|Physical Values]] ==		== [[PhysicalValues/en\|Physical Values]] ==
	Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltage, electric current etc.		Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, [[PhysicalValues/en#Acceleration\|acceleration]], voltage, electric current etc.
	<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m" and "<code>15 inches asMilliMeters</code>" returns "381 mm").		<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m" and "<code>15 inches asMilliMeters</code>" returns "381 mm").

Cg: /* Physical Values */

2024-06-06T16:26:47Z

Physical Values

← Nächstältere Version		Version vom 6. Juni 2024, 16:26 Uhr
Zeile 55:		Zeile 55:

	== [[PhysicalValues/en\|Physical Values]] ==		== [[PhysicalValues/en\|Physical Values]] ==
	Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, ~~voltages~~, electric current etc.		Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltage, electric current etc.
	<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m" and "<code>15 inches asMilliMeters</code>" returns "381 mm").		<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m" and "<code>15 inches asMilliMeters</code>" returns "381 mm").

Cg: /* String */

2024-05-08T16:11:59Z

String

← Nächstältere Version		Version vom 8. Mai 2024, 16:11 Uhr
Zeile 4:		Zeile 4:
	== [[String API Functions \| String]] ==		== [[String API Functions \| String]] ==

	Strings are sequences of characters. Expecco uses and supports the Unicode encoding standard and supports the whole unicode range. However, not all fonts will contain all characters, resulting in some missing characters being drawn with a replacement char (typically a box-like rectangle). The concrete details depend on the operating system and the set of installed fonts.		Strings are sequences of characters. Expecco uses and supports the Unicode encoding standard and supports the whole unicode range. <br>However, not all fonts will contain all characters, resulting in some missing characters being drawn with a replacement char (typically a box-like rectangle) in text windows.<br>The concrete details depend on the operating system and the set of installed fonts.

	String instances inherit a lot of functionality from String's superclasses: SequenceableCollection and Collection. Thus, all functions found there (enumeration, mapping, filtering, searching etc.) can also be applied to strings.		String instances inherit a lot of functionality from String's superclasses: SequenceableCollection and Collection. Thus, all functions found there (enumeration, mapping, filtering, searching etc.) can also be applied to strings.

Cg am 18. Mai 2023 um 06:45 Uhr

2023-05-18T06:45:04Z

← Nächstältere Version		Version vom 18. Mai 2023, 06:45 Uhr
Zeile 1:		Zeile 1:
	This document lists most useful (and most often needed) classes and functions.		This document lists most useful (and most often needed) classes and functions.
	Be aware, that there are many more to be found in either the class references or via the builtin class browser.		Be aware, that there are many more to be found in either the class references or via the builtin [[Tools_ClassBrowser/en \| class browser]].

	== [[String API Functions \| String]] ==		== [[String API Functions \| String]] ==

Cg: /* Date & Time */

2023-05-18T04:14:38Z

Date & Time

← Nächstältere Version		Version vom 18. Mai 2023, 04:14 Uhr
Zeile 49:		Zeile 49:

	== [[Date & Time]] ==		== [[Date & Time]] ==
	Expecco provides a number of time related support classes: TimeDuration, Time, Date and Timestamp (aka. ''TimeAndDate'') ~~both~~ for local, UTC and timezone ~~specifiy~~. Although timestamps support picosecond precision, current operating systems will only provide milli or microsecond resolution timestamps. However finer resolution values may come from exact measurement devices or be computed in technical/physical processes.		Expecco provides a number of time related support classes: TimeDuration, Time, Date and Timestamp (aka. ''TimeAndDate'') for local, UTC and timezone specific. Although timestamps support picosecond precision, current operating systems will only provide milli or microsecond resolution timestamps. However finer resolution values may come from exact measurement devices or be computed in technical/physical processes.

	Read more: [[Date_and_Time_API_Functions\|Date and Time API Functions]]<br>		Read more: [[Date_and_Time_API_Functions\|Date and Time API Functions]]<br>

Cg: /* Collection */

2023-05-18T04:12:31Z

Collection

← Nächstältere Version		Version vom 18. Mai 2023, 04:12 Uhr
Zeile 16:		Zeile 16:

	Collection is an abstract class, serving as a superclass for a number of useful concrete classes (such as Set, Dictionary, Tree, SortedCollection, String etc.)		Collection is an abstract class, serving as a superclass for a number of useful concrete classes (such as Set, Dictionary, Tree, SortedCollection, String etc.)
	It is useful to get a feeling of the set of operations provided there (there is a lot!), so you should not have to reinvent the wheel.		It is useful to get a feeling of the set of operations provided there (there are a lot!), so you should not have to reinvent the wheel.

	Read more: [[Collection_API_Functions\|Collection API Functions]]<br>		Read more: [[Collection_API_Functions\|Collection API Functions]]<br>

Cg: /* Physical Values */

2022-11-09T16:12:19Z

Physical Values

← Nächstältere Version		Version vom 9. November 2022, 16:12 Uhr
Zeile 56:		Zeile 56:
	== [[PhysicalValues/en\|Physical Values]] ==		== [[PhysicalValues/en\|Physical Values]] ==
	Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltages, electric current etc.		Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltages, electric current etc.
	<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m") or "<code>15 inches asMilliMeters</code>" ~~(which gives:~~ "381 mm").		<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m" and "<code>15 inches asMilliMeters</code>" returns "381 mm").

	Read more: [[PhysicalValues/en\|PhysicalValues]]<br>		Read more: [[PhysicalValues/en\|PhysicalValues]]<br>

Cg: /* Physical Values */

2022-11-09T16:11:44Z

Physical Values

← Nächstältere Version		Version vom 9. November 2022, 16:11 Uhr
Zeile 56:		Zeile 56:
	== [[PhysicalValues/en\|Physical Values]] ==		== [[PhysicalValues/en\|Physical Values]] ==
	Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltages, electric current etc.		Since 20.1, expecco supports an additional framework to represent physical values, such as mass (in kg), length (in meters), velocity, acceleration, voltages, electric current etc.
	<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m")		<br>Beside being able to do arithmetic as in <code>3.0 kiloMeter / 20 minutes</code> (which gives "2.5 m/s") they can also be used for conversion between metric and imperial unit systems (eg. "<code>10 nauticalMiles asMeters</code>" gives the answer "18520 m") or "<code>15 inches asMilliMeters</code>" (which gives: "381 mm").

	Read more: [[PhysicalValues/en\|PhysicalValues]]<br>		Read more: [[PhysicalValues/en\|PhysicalValues]]<br>

Cg: /* Filename */

2022-11-09T16:03:16Z

Filename

← Nächstältere Version		Version vom 9. November 2022, 16:03 Uhr
Zeile 23:		Zeile 23:
	== [[Filename API Functions \| Filename]] ==		== [[Filename API Functions \| Filename]] ==

	Although strings could be used to represent file names and pathes, expecco uses instances of a specialized class called "''Filename''" to represent those. Filename instances know about any details of the underlying operating system (such as the directory separator, any naming restrictions etc.) and also provide a number of useful functions for file and directory access. Filename provides a portable representation, so that code can run on both Windows and Unix unchanged.		Although strings could be used to represent file names and pathes, expecco uses instances of a specialized class called "''Filename''" to represent those. Filename instances know about any details of the underlying operating system (such as the directory separator, any naming restrictions etc.) and also provide a number of useful functions for file and directory access. Filename provides a portable representation, so that code can run on both Windows and Unix unchanged (that is: use "/" in filenames when possible. On a Windows machine, these will be replaced internally by "\" characters).

	Read more: [[Filename_API_Functions\|Filename API Functions]]<br>		Read more: [[Filename_API_Functions\|Filename API Functions]]<br>