You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by GitBox <gi...@apache.org> on 2022/03/03 17:56:52 UTC

[GitHub] [daffodil-vscode] mbeckerle commented on issue #5: Handle step in/out commands

mbeckerle commented on issue #5:
URL: https://github.com/apache/daffodil-vscode/issues/5#issuecomment-1058325651


   I define step in/step out in terms of where it would stop for some equivalent breakpoint. 
   
   Step in means stop as if you opened the current element's definition, found the first child element, and put a breakpoint on it and then continued. (But without having to put the breakpoint on it.)
   
   Step out means stop as if you put a breakpoint on the parent element declaration and proceeded. 
   
   I am assuming here that we have such a stopping place, we have a start and and end, so a breakpoint there would cause the debugger to stop after creating the empty element, and to stop again after filling in the contents (simple or complex) of the element.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@daffodil.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org