From: thefadden@gmail.com   
      
   On Monday, September 6, 2021 at 6:40:33 AM UTC-7, Andrew Roughan wrote:   
   > I assumed code hint needed to be used on a block.   
      
   A couple of versions back I stopped calling them "hints", because pretty much   
   everybody who used the program made similar assumptions.  "Code start point"   
   more accurately describes their purpose.  You don't need to identify the end   
   of the code section or    
   any bytes between because the computer can do that for you.   
      
   > It was certainly quicker   
   to mark all code as code than to have to mark each start point as code.   
      
   The SourceGen approach is to assume that everything it can't explicitly reach   
   is data.  I think a lot of people are used to simple disassemblers (e.g. the   
   system monitor) that assume everything is code until you tell it otherwise,   
   and expect to manually    
   exclude data areas.  It's a question of building up the code areas rather than   
   stripping out the data.   
      
   My experience so far has been that SourceGen finds all the code without any   
   help except when (1) JSRs are followed by inline data, or (2) there's a jump   
   table of some sort (usually LDA/PHA/LDA/PHA/RTS, sometimes indirect JMP, but   
   generally easy to spot).    
    The former can be automated and the latter can be formatted with a single   
   command that will apply the code start tags for you.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)