Difference between revisions of "Constref"
(Deleted category because it placed in template) |
(shorted example line len (too wide), text fixes) |
||
Line 9: | Line 9: | ||
procedure test_cr(constref cr: longint); | procedure test_cr(constref cr: longint); | ||
begin | begin | ||
− | writeln(' | + | writeln('Parameter 5 has been passed by reference: ', cr ); |
end; | end; | ||
− | |||
− | |||
begin | begin | ||
Line 19: | Line 17: | ||
test_cr(x); | test_cr(x); | ||
end. | end. | ||
− | |||
− | |||
</source> | </source> | ||
− | |||
It is like the [[Const | const]] parameter qualifier. This qualifier informs the compiler that within the entire program there is no code that will change the value of the parameter. | It is like the [[Const | const]] parameter qualifier. This qualifier informs the compiler that within the entire program there is no code that will change the value of the parameter. | ||
− | This means that not only the ''parameter'', but also the ''variable'' | + | This means that not only the ''parameter'', but also the ''variable'' (in above example: x) passed by the caller (e.g. a global var) is not changed until the call with the constref parameter has returned. |
− | |||
In addition to being like [[Const | const]] parameter qualifier, the '''constref''' qualifier enforces that the parameter is passed by reference. | In addition to being like [[Const | const]] parameter qualifier, the '''constref''' qualifier enforces that the parameter is passed by reference. | ||
This differs from the [[Const | const]] parameters, which may be passed as reference or value depending on what the compiler thinks is best. | This differs from the [[Const | const]] parameters, which may be passed as reference or value depending on what the compiler thinks is best. | ||
− | |||
The [[FPC_New_Features_2.6.0#Constref_parameter_modifier | new feature notes]] for version 2.6 suggest that this can be used for interfacing with external routines in other languages, where this type of parameter passing is required. | The [[FPC_New_Features_2.6.0#Constref_parameter_modifier | new feature notes]] for version 2.6 suggest that this can be used for interfacing with external routines in other languages, where this type of parameter passing is required. | ||
Other uses of constref may hinder the compiler from optimizing code. | Other uses of constref may hinder the compiler from optimizing code. | ||
− | |||
− | |||
== See also == | == See also == | ||
* [[Const|const]] | * [[Const|const]] | ||
* [[Var|var]] | * [[Var|var]] |
Revision as of 23:32, 3 May 2019
│
English (en) │
français (fr) │
Version 2.6 of Free Pascal added the constref parameter qualifier.
program call_method;
var x : longint ;
procedure test_cr(constref cr: longint);
begin
writeln('Parameter 5 has been passed by reference: ', cr );
end;
begin
test_cr(5);
x:=6;
test_cr(x);
end.
It is like the const parameter qualifier. This qualifier informs the compiler that within the entire program there is no code that will change the value of the parameter.
This means that not only the parameter, but also the variable (in above example: x) passed by the caller (e.g. a global var) is not changed until the call with the constref parameter has returned.
In addition to being like const parameter qualifier, the constref qualifier enforces that the parameter is passed by reference.
This differs from the const parameters, which may be passed as reference or value depending on what the compiler thinks is best.
The new feature notes for version 2.6 suggest that this can be used for interfacing with external routines in other languages, where this type of parameter passing is required. Other uses of constref may hinder the compiler from optimizing code.