Adding Pascal language with FPC (Free Pascal Compiler) #64
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added Pascal programming language entry to the table and example.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for the Pascal programming language to the CodeX API by integrating the Free Pascal Compiler (FPC). This expands the API's capabilities, allowing users to execute Pascal code snippets directly.
Key Changes:
New Language Support: Users can now specify "language": "pas" in their API payload to execute Pascal code.
Updated Documentation: The README.md has been updated to include Pascal in the list of supported languages, with its corresponding payload identifier.
Backend Integration: The necessary logic has been added to the server's code execution handler to correctly route, compile (using fpc), and run Pascal source code securely within the existing Docker environment.
Consistent Output: The execution results are formatted to match the existing JSON response structure, ensuring a seamless experience for API consumers.