Recent

Author Topic: Need testers for Pascal-Editor-Macros (latest trunk)  (Read 1771 times)

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9792
  • Debugger - SynEdit - and more
    • wiki
Need testers for Pascal-Editor-Macros (latest trunk)
« on: September 17, 2019, 11:16:58 pm »
Anyone using lazarus svn trunk and
  https://wiki.lazarus.freepascal.org/Editor_Macros_PascalScript

Please re-test all your macros, and report any breakage. (Or hopefully the absence thereof) / Compared to previous version.

Backup (in your primary config path): EditorMacros.xml  (this contains your macros, in the worst case....)


I made some big changes in
Revision: 61896
Date: 17 September 2019 22:21:38
EditorMacroScript: Use "internal" (none-native) calling for object methods


Thanks for any feedback.

Bart

  • Hero Member
  • *****
  • Posts: 5275
    • Bart en Mariska's Webstek
Re: Need testers for Pascal-Editor-Macros (latest trunk)
« Reply #1 on: September 18, 2019, 12:15:36 am »
Shouldn't those pointers be codepointers?

Bart

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9792
  • Debugger - SynEdit - and more
    • wiki
Re: Need testers for Pascal-Editor-Macros (latest trunk)
« Reply #2 on: September 18, 2019, 01:03:17 am »
Which pointers exactly?

Bart

  • Hero Member
  • *****
  • Posts: 5275
    • Bart en Mariska's Webstek
Re: Need testers for Pascal-Editor-Macros (latest trunk)
« Reply #3 on: September 18, 2019, 11:11:54 pm »
Never mind (as long as Lazarus won't support 16/8 bit platforms)  %)

Bart

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 11383
  • FPC developer.
Re: Need testers for Pascal-Editor-Macros (latest trunk)
« Reply #4 on: September 19, 2019, 04:47:32 pm »
Note that FPC trunk with Linux 32-bit also might require retesting

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 9792
  • Debugger - SynEdit - and more
    • wiki
Re: Need testers for Pascal-Editor-Macros (latest trunk)
« Reply #5 on: September 19, 2019, 05:34:03 pm »
Note that FPC trunk with Linux 32-bit also might require retesting
That calling convention change is why I did the change.
It no longer simulates native function calls. Instead it calls a pre-defined (call generated by the compiler, during compilation) function, and hands over the arguments as a list.

But yes, it will need testing, like everything in life...
« Last Edit: September 19, 2019, 07:39:11 pm by Martin_fr »

 

TinyPortal © 2005-2018