Breakpoints set in the pseudocode of functions

[François Vogel]

Hi Serge,

I have seen that in order to close bug 2542 you wrote macros 
add_profiling, remove_profiling, and so on, that use the bytecode of 
the function to profile. This looks very nice to me.

I was wondering if the same approach could be used with some advantage 
to set/remove breakpoints in functions instead of using set/delbpt? I 
remember you mentioned such an approach a few years ago, but I think 
this never took shape.

Currently setbpt/delbpt maintain an internal array of breakpoints 
(function names and line numbers), and this array is checked during 
execution of each line against the current execution point.

The new approach would be to store a special pseudocode after each 
line of each function, telling whether the execution should stop at 
this point or not.

See also http://bugzilla.scilab.org/show_bug.cgi?id=884#c1

I think you wrote me privately a long time ago that such a new 
approach would have some other advantages, but I can't remember which 
ones exactly at the moment.

Do you have any thoughts on this old idea in the light of what you 
just achieved for profiling with pseudocodes?

Thanks,
Francois