Test suite results for test file tbs/tb0157.pp

Test run data :

Run ID:
Operating system: linux
Processor: i386
Version: 3.3.1
Fails/OK/Total: 238/9417/9655
Version: 3.3.1
Full version: 3.3.1-15587-g490a8c68ea-unpushed
Comment: -XR/home/muller/sys-root/i386-linux -Xd -Xr/home/muller/sys-root/i386-linux
Machine: cfarm13
Category: 1
SVN revisions: 490a8c68ea:8b7dbb81b1:3f8bbd3b00:2f9ed0576e
Submitter: muller
Date: 2024/04/19 11:03:00
Previous run: 934303
Next run: 935638

Hide skipped tests

Hide successful tests

Test file "tbs/tb0157.pp" information:

t_id 396
t_adddate 2003/10/03
t_result 0
t_knownrunerror 0

Detailed test run results:

tr_idruntr_oktr_skiptr_result
443813125934990TrueFalseSuccessfully run

Record count: 1

No log of 934990.

Source:

{ Old file: tbs0188.pp }
{ can't print function result of procedural var that returns a function. Not a bugs : wrong syntax !! See source (PM) }

{ this are no bugs, just wrong
  understanding of FPC syntax }

type testfunc = function:longint;

var f : testfunc;

var test: testfunc;

function test_temp: longint;
begin
  test_temp:=12;
end;

procedure sound(test: testfunc);
begin
  {writeln(test); this is wrong because
   test is the function itself and write does not know how to
   output a function !
   to call test you must use test() !! }
  writeln(test());
end; { proc. sound }

var i : longint;
begin
  i:=test_temp;
  f:=@test_temp;
  if f()<>i then
    begin
       Writeln('error calling f');
       Halt(1);
    end;

  { this works for FPC
   sound(test_temp);
  but the correct syntax would be }
  sound(@test_temp);
  { imagine if a function would return its own type !! }

  { for f var this is correct also ! }
  sound(f);
end.

Link to SVN view of tbs/tb0157.pp source.