From: cross@spitfire.i.gajendra.net   
      
   In article <10ffuoe$11uj0$2@dont-email.me>,   
   Arne Vajhøj   wrote:   
   >On 11/17/2025 3:25 AM, Marc Van Dyck wrote:   
   >> Arne Vajhøj wrote on 14/11/2025 :   
   >>> So for VMS Pascal:   
   >>> * search for "::"   
   >>> * search for "UNSAFE"   
   >>> * multi line regex search for "RECORD.*CASE.*END"   
   >>> and setup extra code reviews for all hits.   
   >>>   
   >>> Anything else to look for?   
   >   
   >> For languages that are supported, would VAXset's Source Code Analyzer be   
   >> of any help to identify such potential weaknesses ? I have been using   
   >> it regularly, but never for that...   
   >   
   >It do not see anything in the SCA manual.   
   >   
   >And when SCA was created the focus was on other things.   
   >   
   >But I have never used SCA myself, so maybe there is something.   
      
   This is an area where modern LSP integration between editors and   
   other tooling really shines: again, only using Rust as an   
   example, one can configure the popular editors to render   
   `unsafe` code in a different font/color/etc, which can be a huge   
   help.  Of course, language servers for other languages can be   
   configured similarly, and since there's a clear separation   
   between language server and editor, this technique can be   
   employed across many editor/language combinations (provided that   
   somebody does the work).   
      
   It would be interesting to do an LSP implementation, for, say,   
   VSI Pascal: one could imagine using e.g. VSCode with a local   
   proxy agent talking to a language server running on VMS.   
      
   	- Dan C.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)