Not widely known problem in programming? (Developers)
> I don't think a compiler is going to help much in this case.
You can try to generate warnings with static analysis (in compiler or with a separate tool) if a pointer to the stack is returned. But this is probably not watertight, though probably would cover many common accidental cases.
Peganza used to have a static analysis tool for Pascal/Delphi. A former employer had a license for it, and it seems they have expanded since. It might be worth looking at if they implemented something like that.
AQTime might also have something
Complete thread:
- Not widely known problem in programming? - Laaca, 27.03.2021, 20:06 (Developers)
- Not widely known problem in programming? - ecm, 27.03.2021, 20:30
- Not widely known problem in programming? - tkchia, 28.03.2021, 08:02
- Not widely known problem in programming? - marcov, 28.03.2021, 17:44
- Not widely known problem in programming? - bretjohn, 29.03.2021, 20:03
- Not widely known problem in programming? - Laaca, 29.03.2021, 22:24
- Not widely known problem in programming? - bretjohn, 29.03.2021, 23:02
- Not widely known problem in programming? - marcov, 30.03.2021, 12:05
- Not widely known problem in programming? - bretjohn, 29.03.2021, 23:02
- Not widely known problem in programming? - ecm, 29.03.2021, 22:26
- Not widely known problem in programming? - Laaca, 29.03.2021, 22:24
- Not widely known problem in programming? - tkchia, 28.03.2021, 08:02
- Not widely known problem in programming? - ecm, 28.03.2021, 21:52
- Not widely known problem in programming? - Laaca, 29.03.2021, 05:04
- Not widely known problem in programming? - ecm, 27.03.2021, 20:30