# PVS\-Studio 7\.43: Unreal Engine support in Team license, extended MISRA C\+\+ 2023, Zephyr SDK support, and more PVS\-Studio 7\.43 has been released\. This version features expanded support for MISRA C\+\+ 2023, Unreal Engine integration in the Team license, Zephyr SDK support and much more\. ![1386_release_7_43/image1.png](https://import.viva64.com/docx/blog/1386_release_7_43/image1.png) ## Unreal Engine support in the Team license Good news for Unreal Engine developers: analysis of Unreal Engine projects is no longer limited to the [Enterprise license](https://pvs-studio.com/en/order/license/)\. Starting with PVS\-Studio 7\.43, this functionality is also available in the Team license\. [Learn more about the analysis of Unreal Engine projects](https://pvs-studio.com/en/docs/manual/0043/) ## MISRA C\+\+ 2023 We continue to expand our support for MISRA C\+\+ 2023\. In this update, we've adapted 12 existing diagnostic rules from the MISRA group to comply with the MISRA C\+\+ 2023 standard\. [Lean more about the support of the MISRA standard](https://pvs-studio.com/en/pvs-studio/sast/misra/) ## Zephyr SDK support PVS\-Studio 7\.43 can now analyze projects that use compilers from the Zephyr SDK\. You can inspect such projects via `compile_commands.json` or build monitoring\. [Learn more](https://pvs-studio.com/en/docs/manual/6615/) about the integration ## Analyzer improvements We've enhanced the interprocedural loop analysis in the C and C\+\+ analyzer\. Now the analyzer can evaluate canonical loops and factor in possible value ranges of variables\. The C\# analyzer now supports \.NET SDK version 10\.0\.300 on Linux and macOS\. [Learn more about the analyzer usage on these platforms](https://pvs-studio.com/en/docs/manual/0035/)\. > \*\*Reminder\*\*: Our Early Access Program for JavaScript and Go analyzers and the Atlas code quality management platform is still open\\\. You can now also evaluate PVS\\\-Studio for TypeScript\\\. > > > > If you'd like to participate, simply, \[please fill out the form on our website\]\(https://pvs\-studio\.com/en/pvs\-studio\-eap/\#form\-eap\)\\\. ## New diagnostic rules ### Java * [V6135](https://pvs-studio.com/en/docs/warnings/v6135/)\. The return value of the 'finally' block overrides return values of 'try' and 'catch' blocks\. ## Articles Here is our traditional roundup of blog articles\! Over the past two months, we've posted articles exploring vibe\-coding, covering alignment in C\+\+, error handling in Go, and the new features of Java 26, celebrating the evolution of our mascot Cody, and much more\. Below is the full list\. ### C and C\+\+ * [Let's check vibe code that acts like optimized C\+\+ but is actually a mess](https://pvs-studio.com/en/blog/posts/cpp/1366/) * [Silent foe or quiet ally: Brief guide to alignment in C\+\+\. Part 3](https://pvs-studio.com/en/blog/posts/cpp/1369/) * [PVS\-Studio in CMake: It's official now\!](https://pvs-studio.com/en/blog/posts/cpp/1374/) * [C\+\+ digest: News, helpful resources, & your own programming language as bonus](https://pvs-studio.com/en/blog/posts/cpp/1376/) * [Real\-world C\+\+ projects built with GenAI: do they exist?](https://pvs-studio.com/en/blog/posts/cpp/1379/) ### C\# * [AI integrations: rely or verify? Checking Semantic Kernel](https://pvs-studio.com/en/blog/posts/csharp/1367/) * [Bugs and suspicious code fragments in \.NET 10](https://pvs-studio.com/en/blog/posts/csharp/1380/) ### Java * [What's new in Java 26](https://pvs-studio.com/en/blog/posts/java/1370/) ### JavaScript * [Error that we had to ignore](https://pvs-studio.com/en/blog/posts/js/1381/) ### Go * [Double AI agents: What's hiding in your Golang code](https://pvs-studio.com/en/blog/posts/go/1377/) * [Error handling in Go: Common pitfalls](https://pvs-studio.com/en/blog/posts/go/1371/) ### Security * [Static code analysis and software time to market](https://pvs-studio.com/en/blog/posts/1373/) ### GameDev * [Game\+\+\. Part 1\.2: C\+\+, game engines, and architectures](https://pvs-studio.com/en/blog/posts/1375/) ### Other * [Evolution of Cody: PVS\-Studio mascot through the years](https://pvs-studio.com/en/blog/posts/1372/) ## Webinars ### Let's make a programming language\. Grammars In our first session, we explored the core building blocks: the lexer, parser, semantic analyzer, and evaluator—how they work and how they fit together\. Now it's time to dive into grammars\. What is a language, really? How can you describe it in a way that a program understands what a sequence of symbols means and what result it should produce? We'll break it down in a clear and practical way—and, of course, get hands\-on with grammars\. ### Let's make a programming language\. Lexer The lexer is the part of the parsing pipeline that operates on terminal symbols\. It takes a raw input stream and turns it into a sequence of tokens—classifying lexemes into meaningful units\. This process, as you know, is called tokenization\. We won't stop at theory\. During the webinar, we'll walk through how a lexer is actually implemented in code\. This session is aimed at developers who want to go beyond using languages and start understanding how they work under the hood\. > Want to see more webinars, we invite you to check out upcoming events on the \[webinar page\]\(https://pvs\-studio\.com/en/webinar/\)\\\. ## Conclusion If you'd like to receive news about PVS\-Studio releases, [subscribe to our newsletter](https://pvs-studio.com/en/subscribe/)\. Do you want to check your project with PVS\-Studio? [Start with a trial license](https://pvs-studio.com/en/pvs-studio/try-free/)\!