US 2026/0064375 A1Published application

System and method for dynamic code parsing and real-time insight generation prior to compilation

OwnerAbhijit Anant Telanginventor

Life of this patent

Estimating the term…

Loading patent…

Abstract

The present invention provides a continuous code monitoring parser integrated with a text editor that continuously monitors, analyzes a code as it is being written and displays warning texts in real-time comprising an event management block including an event generation module and a design time module, a code analysis block including a classifier module, a deconstruction module and an analysis module, a prediction block including a ML module, and an output and feedback block including a text generator and a coding style guide. The steps of dynamic code parsing by the said parser comprises code specification; keyword recognition and categorization; activation and subsequent deactivation of event generation module and design time module; activation of deconstruction module; segregation and clustering of decomposed components, utilization and impact analysis by analyzation module; predicting potential issues and calculating vulnerability scores by the ML module; and providing real-time prescriptive insights and recommendations.

Claims8

Dependent claims

A continuous code monitoring parser integrated with a text editor that performs dynamic code parsing and generates real-time insights on the quality of the code comprising:

an event management block including an event generation module and a design time module,
wherein the event generation module further includes an event generator and an event handler that creates and manages events based on code actions;
wherein the design time module further includes one or more timer that is configured to associate with one or more code blocks and its contained components to track their usage;
wherein the timer starts when a syntactical construct is complete and stops as it discovers an assignment or invocation of a code block, or its contained components;
a code analysis block including a classifier module, a deconstruction module and an analysis module,
wherein the classifier module identifies and categorizes language-specific keywords and constructs including code blocks and its contained components as per the grammar rules of the language being parsed;
wherein the deconstruction module further includes
a code decomposer that divides or breaks down a complex code into several small manageable code blocks, and
a tokenizer that breaks down each decomposed code block into several meaningful units and contained components;
wherein the analysis module further includes a filter that segregates the deconstructed code blocks and its contained components based on usage, dependencies, interference, redundancies and impacts, and
an analyzer that estimates the utilization of the segregated code block and/or its contained components by collectively clustering variables or code blocks or its contained components based on the clustering criteria of idle time, or elapsed time since start of specification, or mean time between success usage and marks each category with a color-coded tag;
a prediction block including a ML module that is configured to learn from historical data to predict potential issues and calculate vulnerability score to warn about the potential impact to the user,
wherein the potential issues include likelihood of information loss, functional loss, compilation and/or run-time errors, and/or interference among code blocks and variables;
an output and feedback block including a text generator and a coding style guide,
wherein the text generator generates and displays warnings and prescriptive texts based on analysis and predictions by the analyzation and ML modules, and
the coding style guide further includes a dashboard with dashlets that are created using web server components wherein the frontend and backend components are integrated using IDE;
wherein the said warning texts includes insights retrieved from the impact analysis stored in the database and the coding style guide provides real-time feedback and visualizations of code quality and usage.

14 more elements

A process of dynamic code parsing with real-time insights on the quality of the code using a parsing component comprises the steps of:

(a) defining or specifying or introducing all the modules of the parsing components;
wherein the modules include an event generation module, a design time module, a classifier module, a deconstruction module, an analysis module, a ML module, a text generator and a coding style guide;
(b) typing or dictating or gesturing code specification;
(c) identifying language specific keywords by the classifier module when a user specifies them as per the grammar rules of the language being parsed, collect identified keywords into a pool of variables, functions, interfaces, classes and structures and filters/extracts and classifies the collected keywords into functional categories including code blocks and its contained components, assignments and conditional checks;
wherein the keywords include but not limited to def, function, public, class, interface, extends, super, if, else, elif, for, while, break, continue, int, float, char, list, dict, try, except, catch, and the like;
(d) the event generation and corresponding event listener or handler module at the start of specification and its subsequent usage as and when reported by the classifier module;
(e) associating a timer from the design time module after the start of an event with any of the specified functional components and starts timing/scheduling/counting;
(f) stopping the timer at the end of specification and its subsequent usage as and when reported by the classifier module and eventually deactivating the design time module at the event end time and assignment/invocation of the specified functional components;
wherein the end of specification is determined by identification of closing delimiters that matches the opening delimiters including indentation, curly braces, angle brackets, square brackets, tags and the like;
wherein the timer records and reports the lapsed time between ideation and usage by storage in the database and subsequent display in the form of a warning;
wherein the timer restarts when the usage of a specified code block and its contained components is revoked or removed;
(g) activating the self-reflecting code decomposer and tokenizer from the deconstruction module wherein the deconstruction module decomposes the recently/newly created functional code block, assignments and conditional checks into its components such as functions, parameters including input and output parameters, and variables recursively until a leaf element is encountered;
wherein the recursive application detects any change in event including a name change, type change, and/or collection change;
(h) parsing the deconstructed code block by the analysis module wherein the filter segregates the deconstructed code blocks and its contained components based on usage, dependencies, complete and incomplete specification, interference, redundancies and impacts, and
the analyzer estimates and records the utilization of the segregated code block and/or its contained components, and linkages between functional code blocks by collectively clustering the timer with its associated code block or its contained components and marks each category with a color-coded tag based on frequency of usage, density of linkages and size,
(i) performing impact analysis on the marked code blocks by the analyzer such that it detects the changes initiated by user to perform changes in functional components and its respective interference in functioning of the impacted code blocks;
wherein the impact analysis for each change event and assignment or removal of values or linkages includes the forecast of potential unknown variable or code block errors, the identification of reference connections that may be lost due to inadvertent changes, the assessment of potential duplicate or scope conflict issues, the evaluation of possible information or functional loss due to type incompatibilities resulting from the change and the anticipation of potential information or functional loss arising from forced value assignments, removals, or revocations;
and
segments code blocks and its contained components in terms of dependency including independent, mutually dependent and/or dependency in one way only;
wherein the intentions include name change, or value change, or type change, or sequence change or relationship change such as change in containership or association with other data structures or variables or code blocks, or value change;
(j) activating the ML module to learn the sequence, co-occurrence, and correlation of associated timers while specifying code blocks, and variables along with their respective count, and type, and their usage;
(k) interpreting the likelihood of information loss, functional loss, compilation and/or run-time errors, and/or interference among code blocks and variables by incorporating the impact analysis from step (i) by the ML module;
(l) predicting a vulnerability score or likelihood by the ML module wherein the predicted vulnerability score is directly proportional to the odds ratio;
(m) generating personalized and prescriptive forewarning and warning texts by the text generator such that it indicates the potential impact on functional code blocks as and when the analyzation module and the ML module are activated;
wherein the warning texts are retrieved from the database;
wherein the warning texts are generated either by introducing a tool specific programming interface or by abstracted query generator;
(n) displaying the generated warning text, interlinkages of the code blocks and variables depicting the code specified at the time, predictions of issues in a coding construct, and details of the impacted code blocks to the user in real-time.

24 more elements

Dependencies are inferred from the claim text.