View Issue Details

IDProjectCategoryView StatusLast Update
0037318FPCRTLpublic2020-07-09 07:39
Reporterrunewalsh Assigned ToSven Barth  
PrioritynormalSeverityminorReproducibilityN/A
Status resolvedResolutionwon't fix 
Summary0037318: Strongly type InitProc and ExitProc
DescriptionExitProc allows you not to call an old ExitProc manually, but instead set the old callback during the execution of your one and RTL will call it again for you, i. e.
var
    oldExitProc: CodePointer;

procedure MyExitProc;
begin
    // do your stuff
    ExitProc := prevExitProc;
end;

prevExitProc := ExitProc;
ExitProc := @MyExitProc;

So with ExitProc, lack of a typing isn't that annoyance.

But InitProc doesn't do it: you must call the previous one manually, and thus cast it to TProcedure.
So.
Why would they be CodePointers and not TProcedures in the first place?
TagsNo tags attached.
Fixed in Revision
FPCOldBugId
FPCTarget-
Attached Files

Issue History

Date Modified Username Field Change
2020-07-09 01:41 runewalsh New Issue
2020-07-09 07:39 Sven Barth Assigned To => Sven Barth
2020-07-09 07:39 Sven Barth Status new => resolved
2020-07-09 07:39 Sven Barth Resolution open => won't fix
2020-07-09 07:39 Sven Barth FPCTarget => -
2020-07-09 07:39 Sven Barth Note Added: 0123836