Source Code Correction Support Device for Skip-in-Reading Errors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In software development, errors in source code can lead to compilation skips, resulting in increased workload and processing costs due to repeated compilations and potential new errors introduced by corrections, as existing techniques fail to effectively handle errors causing skip-in-reading events.

Innovation Solution

A computer-readable storage medium and method that analyzes source code, generates corrected code by addressing errors causing skip-in-reading, and performs re-compilation to ensure complete analysis, reducing the number of compilation cycles and correcting errors without introducing dual definitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error correction is performed based on dictionary lookup, then error recovery is supported, but errors causing skip-in-reading events cannot be properly detected or corrected

Engineering Contradiction:
Improveerror detection accuracyVSAvoidhandling capability for skip-in-reading errors
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent divides the error correction process into two distinct phases: a first analysis that performs initial error detection with basic rules, and a second analysis that specifically handles skip-in-reading events. This segmentation allows each phase to specialize in different error types, improving overall detection accuracy while maintaining the ability to handle complex skip-in-reading errors that the initial analysis misses.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If repeated compilations are performed to correct errors, then source code errors are eventually fixed, but workload and processing costs increase

Engineering Contradiction:
Improvesource code correctnessVSAvoidcompilation efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent performs preliminary identification of skip-in-reading errors during the first analysis phase, before actual compilation occurs. By detecting and flagging these errors in advance using the specific rules stored in the storage unit, the system prevents the need for multiple re-compilations, thereby reducing overall workload and processing costs while ensuring source code correctness.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If error corrections are applied without re-analysis, then correction speed is improved, but new errors may be introduced or existing errors missed

Engineering Contradiction:
Improvecorrection processing speedVSAvoidcorrection accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the results of the first analysis are fed into the second analysis, which specifically checks for skip-in-reading events. The corrected source code then undergoes verification through the second analysis to ensure that corrections did not introduce new errors or miss existing ones. This feedback loop maintains high correction accuracy while preserving processing speed through the specialized division of labor between the two analysis phases.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10402304B2Non-transitory computer-readable storage medium, correction support method and correction support device
Publication Date: 2019.09.03 FUJITSU LTD
  • US10402304B2 patent drawing
  • US10402304B2 patent drawing
  • US10402304B2 patent drawing

AI summary

A non-transitory computer-readable storage medium storing a program that causes a computer to execute a process, the process including receiving a source code, performing a first analysis that analyzes the received source code in accordance with a specific rule, generating a new source code when at least one error is detected in the first analysis, the new source code having the at least one error corrected, performing a second analysis that analyzes the generated new source code in accordance with the specific rule when the at least one error causes the first analysis to skip analysis of a portion of the received source code, and outputting the new source code when the at least one error does not cause the first analysis to skip the analysis of the portion of the received source code.