pseudocode-extractor

Pseudocode Extractor

Overview

Transform source code from any programming language into clear, language-agnostic pseudocode that captures the essential logic and control flow while removing syntax-specific details.

Extraction Process

1. Analyze Input Code

First, identify the programming language and understand the code structure:

• Recognize functions, classes, methods, and modules
• Identify control flow structures (loops, conditionals, error handling)
• Note data structures and their relationships
• Understand the overall algorithmic approach

2. Extract Core Logic

Focus on WHAT the code does, not HOW it's implemented:

Preserve:

• Function/method names and their purpose
• Control flow (if/else, loops, switch/case logic)
• Logical operations and conditions
• Data transformations and assignments
• Function calls and their relationships
• Class structures and inheritance relationships
• Key variable names that convey meaning

Filter out:

• Language-specific syntax (semicolons, braces, keywords)
• Type declarations and annotations
• Import/include statements (unless critical to understanding)
• Error handling boilerplate (try/catch unless the logic is important)
• Memory management details
• Language-specific idioms
• Verbose getter/setter methods
• Standard library implementation details

3. Format Pseudocode

Use clear, readable pseudocode conventions:

Structure:

FUNCTION function_name(parameters)
    // High-level description of what function does

    IF condition THEN
        action
    ELSE IF another_condition THEN
        another_action
    ELSE
        default_action
    END IF

    FOR EACH item IN collection DO
        process item
    END FOR

    WHILE condition DO
        action
    END WHILE

    RETURN result
END FUNCTION

Conventions:

• Use UPPERCASE for keywords (FUNCTION, IF, FOR, WHILE, RETURN, etc.)
• Use descriptive names in lowercase or camelCase
• Indent to show nesting and structure
• Use comments to explain complex logic
• Keep operations at a high level of abstraction
• Use mathematical notation where appropriate (←, ≠, ≤, etc.)