Thanks! For a start this is indeed useful and yup, this looks like this would belong as a part of the OSDK library.
Obviously, it would be even better if we could have scope-profiling by simply defining profiling class instances but this would require a c++ compiler and I guess we are not there yet.
For those who are curious, this would look like this:
Code: Select all
void my_function(int a, int b)
{
PROFILE(my_function); // <- a macro, actually translates to -> ScopeProfiler profiler_L122_my_function("my_function")
while ( whatever)
{
PROFILE(loop); // translates to -> ScopeProfiler profiler_L126_loop("loop")
// ...
}
}
Chema wrote: ↑Tue Oct 30, 2018 2:41 pm
It is a pity that nobody jumped into the expansion I proposed to Oricutron. My idea was adding support for external tools, at least, receive commands and send data back to an external application (using a socket or any other method). I suggested this to the author of a spectrum emulator and the results were incredible.
Actually, DBug did and suggested a GDB extension for Oricutron, which is kinda the generalization of your suggestion, and which I find absolutely great.
The advantage of the GDB standard is that it is supported by many IDEs (Visual Studio for example), so this would allow to debug Oric applications from our preferred IDE.
Maybe we should create an official issue/request on the GitHub page and vote it up?
iss wrote: ↑Tue Oct 30, 2018 9:01 am
Just small addition for Oricutron's internal cycle counter - you can control it with breakpoints too.
For more info see my post
here and the
ReadMe.txt.
I see, thanks!
)!