Difference between revisions of "sysutils"
From Lazarus wiki
Jump to navigationJump to searchm (Improved English grammar) |
(partially undo revision 142563 by Trev (talk): avoid redlinks unless necessary, consider functionality as “notable” if there is a wiki page, don’t omit explanatory information) |
||
| Line 7: | Line 7: | ||
== Notable functionality == | == Notable functionality == | ||
| − | |||
* [[Format function|<syntaxhighlight lang="pascal" inline>format</syntaxhighlight>]] | * [[Format function|<syntaxhighlight lang="pascal" inline>format</syntaxhighlight>]] | ||
| + | * [[Executing External Programs#SysUtils.ExecuteProcess|<syntaxhighlight lang="pascal" inline>executeProcess</syntaxhighlight> for executing external programs]] | ||
| + | * several routines ensuring productive use of [[TDateTime|<syntaxhighlight lang="pascal" inline>tDateTime</syntaxhighlight>]] | ||
* {{Doc|package=RTL|unit=sysutils|identifier=typehelpers|text=type helpers for all basic data types}} | * {{Doc|package=RTL|unit=sysutils|identifier=typehelpers|text=type helpers for all basic data types}} | ||
| + | * [[FreeAndNil|<syntaxhighlight lang="pascal" inline>freeAndNil</syntaxhighlight>]] | ||
| + | * routines to access [[Command line parameters and environment variables#Environment variables|environment variables]] | ||
== Caveats == | == Caveats == | ||
| + | {{Doc|package=RTL|unit=system|identifier=runtimeerrors|text=If the <syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> unit is included}}, all [[runtime error|run-time errors]] become [[Exceptions|exceptions]], which virtually forces you to use a [[Compiler Mode|compiler mode]] (or [[modeswitch|mode switch]]) that allows exception treatment. | ||
| + | To catch an exception by its name you will need to include <syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> in every unit that may throw an exception, even though the unit itself does not use any of the included system utilities. | ||
| − | + | If [[Size Matters|size matters]], using <syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> is by design not the smartest choice. | |
| − | |||
== See also == | == See also == | ||
| − | |||
* {{Doc|package=RTL|unit=sysutils|text=<syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> reference}} | * {{Doc|package=RTL|unit=sysutils|text=<syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> reference}} | ||
* [http://docwiki.embarcadero.com/Libraries/Sydney/en/System.SysUtils Delphi’s <syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> unit] | * [http://docwiki.embarcadero.com/Libraries/Sydney/en/System.SysUtils Delphi’s <syntaxhighlight lang="pascal" inline>sysUtils</syntaxhighlight> unit] | ||
| − | * [[libc|<syntaxhighlight lang=" | + | * [[libc library|<syntaxhighlight lang="c" inline>libc</syntaxhighlight> library]] <!-- similar in design --> |
* [[System unit|<syntaxhighlight lang="pascal" inline>system</syntaxhighlight> unit]] | * [[System unit|<syntaxhighlight lang="pascal" inline>system</syntaxhighlight> unit]] | ||
Revision as of 01:22, 23 January 2021
│
English (en) │
Esperanto (eo) │
français (fr) │
The unit sysUtils shipped with the FPC’s default run-time library provides many system utilities.
It attempts to be as compatible to Delphi’s sysUtils unit as possible.
However, the FPC version is available on all platforms that the FPC supports.
It does not contain any Windows-related routines or other highly platform-specific functionality.
Notable functionality
formatexecuteProcessfor executing external programs- several routines ensuring productive use of
tDateTime - type helpers for all basic data types
freeAndNil- routines to access environment variables
Caveats
If the sysUtils unit is included, all run-time errors become exceptions, which virtually forces you to use a compiler mode (or mode switch) that allows exception treatment.
To catch an exception by its name you will need to include sysUtils in every unit that may throw an exception, even though the unit itself does not use any of the included system utilities.
If size matters, using sysUtils is by design not the smartest choice.
