Auto fill in Comments

• 
  Hi Mike,
  
  
  I'm not able to reproduce this here. Does it occur within a specific context in a script? If so can you send me the script so I can try it out and see what's happening please?
  
  One thing I would suggest is that if you've switched off the auto-insertion of a closing comment mark then you switch that back on as it makes the comment detection an awful lot more reliable. You'll find it under Auto Insert in the Options dialog.
  
  Comments are slightly problematic in that the parser (actually the lexer) just ignores them completely, which in general is a good thing, however it can make detecting whether or not you're inside one somewhat problematic, particularly in the case of multi-line comments. How far do you scan back/forward for the delimiters?
  
  Please let me know if any of this makes any difference, or if you can provide an example where it doesn't work we may be able to fix it.
  
  
  Thanks,
  Bart

  Bart Read December 15, 2006 06:18

  - 0 +
• 
  Try this:
  

  SELECT *
  FROM dbo.Test
  
  -- this line will not be parsed
  /* -- neither will this line
  here ALL keywords are capitalized, AND the intellisense kicks IN example:
  SELECT TOP 45 *
  FROM dbo.Test
  here nothing happens again */
  

  
  The single line comments are handled correctly, and the lines with the start and end tag of the multi-line comment are ok too.
  
  It's just the lines that do not have the multi-line markers that are a problem.
  
  If the first select query (the one outside the comment) is removed, the intellisense won't kick in.
  
  Hope this helps with finding the bug.
  
  Kind regards and happy holidays,
  Turambar

  Turambar December 15, 2006 10:55

  - 0 +
• 
  Thanks Turambar,
  I'll give it a go.
  Cheers,
  Bart

  Bart Read December 15, 2006 10:55

  - 0 +

Add comment

Please sign in to leave a comment.