[Lazarus] Need testers for Pascal-Editor-Macros (latest trunk)

Sergey Bodrov serbod at gmail.com
Thu Sep 19 09:25:00 CEST 2019


>
> > There can be lot more bugs, but them hides in very bad sources style
> > and formatting.
> > For example, spaces between function name and parameters: inc (i);
> In which package, please?
>
Where TIdeMacroEventReader defined.


> > Please, do proper formatting. Bad formatting makes debugger crazy
> > (with wrong breakpoints ans steps)
> Only line breaks should affect the debugger (space/tab should not, if it
> does an example would be welcome).
>
Example:
if a < b then Delete(a);
// When debugging step-by-step with F8, that line will be skipped in one
step, and it remains unclear, that Delete(a) executed.

if a < b then
  Delete(a);
// When condition is true, debugger step on line with Delete(a) and it can
be skipped with F8 or visited with F7. And breakpoint can be set on desired
condition branch.

Spaces between function name and parameter make function be like a
variable. I personally always add empty parenthesis to every procedure,
function and method, even if they don't have parameters. It helps
distinguish, when indentifier can be stepped in (with F7) or skipped (with
F8) and inspected by watch.

-- 
*Bodrov Sergey*
software development, IT consulting
http://www.serbod.com
*Phone (Belarus):* +375(25)794-21-58
*Skype:* sergey.bodrov1
*e-mail:* serbod at gmail.com, oxotnuk at yandex.ru
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190919/3a9e9f84/attachment-0001.html>


More information about the lazarus mailing list