Recent

Author Topic: [SOLVED]Troubles when converting C .h (Measurement Computing / Digilent device)  (Read 4772 times)

CM630

  • Hero Member
  • *****
  • Posts: 1250
  • Не съм сигурен, че те разбирам.
    • http://sourceforge.net/u/cm630/profile/
Re: Troubles when converting C .h (Measurement Computing / Digilent device)
« Reply #15 on: January 15, 2025, 12:51:27 pm »
...

Edit: Now I see: To invoke it just put () at the end:
Code: Pascal  [Select][+][-]
  1.  I := cbIgnoreInstaCal();
Thanks! It works now... I do not remember ever putting () after calling a function in Pascal :o
Лазар 4,0RC2 32 bit (sometimes 64 bit); FPC3,2,2

cdbc

  • Hero Member
  • *****
  • Posts: 1832
    • http://www.cdbc.dk
Hi
I got bitten by that, especially if the receiving variable is a pointer  %)
Since then with pointer types I remember the '()'  ;D
Regards Benny
If it ain't broke, don't fix it ;)
PCLinuxOS(rolling release) 64bit -> KDE5 -> FPC 3.2.2 -> Lazarus 2.2.6 up until Jan 2024 from then on it's: KDE5/QT5 -> FPC 3.3.1 -> Lazarus 3.0

bytebites

  • Hero Member
  • *****
  • Posts: 698
This is sad design flaw in Pascal.

PascalDragon

  • Hero Member
  • *****
  • Posts: 5858
  • Compiler Developer
This is sad design flaw in Pascal.

It's an explicit design decision in the FPC and ObjFPC modes, so that it can be better differentiated between calling the function and copying the value of the function pointer.

bytebites

  • Hero Member
  • *****
  • Posts: 698
This is sad design flaw in Pascal.

It's an explicit design decision in the FPC and ObjFPC modes, so that it can be better differentiated between calling the function and copying the value of the function pointer.

I mean design flaw is that function call does not require ().

 

TinyPortal © 2005-2018