[Feature Rqst] Prevent PL/SQL Dev from setting illegal breakpoints

[Ed Holloman]

Version 6.0.3.893 (MBCS)
Windows XP version 6.0 (build 2600) Service Pack 2

Hi,

I've noticed that PL/SQL Dev will allow you to set a breakpoint pretty much anywhere. It's not until you attempt to debug a test script that it tells you that there are illegal breakpoints. It displays a dialog, but doesn't take you to the illegal breakpoint, it just runs past it. There doesn't seem to be any way to determine what is an illegal breakpoint (breakpoint on a WHEN condition in a case statement, is apparently illegal, for example). If you go to Debug -> Modify Breakpoints, the illegal ones don't look any different than any others.

So, why not just prevent the user from setting illegal breakpoints in the first place?

Regards,

Ed Holloman

 

[Marco Kalter]

I don't think we can prevent it, because we only know the breakpoint is invalid when you start the debugger. However, we can provide a more accurate error message.