Skip to content
This repository was archived by the owner on Oct 4, 2026. It is now read-only.

YPSH v10.2

Choose a tag to compare

@nercone-dev nercone-dev released this 20 Oct 08:29
· 46 commits to main since this release

This release includes new dependencies, which may cause build failures.
If any issues arise, we will address them in a new release as soon as they are identified.
If no issues are found, the release will be officially added to the stable channel.

Comment Format Changes

The previous section-specific comment format took up approximately three lines and took up a lot of space, so we have simplified it.
This change has no effect on the YPSH language itself; it only affects the runtime source code.

Memory Management Function

Memory management functions have been added.
These functions can be accessed via the memory module and imported with import("memory").
The auto_gc and collect_after_toplevel options have been added to the runtime.options category in the configuration file, allowing you to customize their behavior.

Exception Handling

Exception Display Changes
The display added to stdout/stderr when an exception occurs has been changed.
The coloring is set according to the exception level.

Changes to Exception Levels
Until now, there were only four levels: E (Error), W (Warning), I (Info), and D (Debug). Now, we've added a new level: C (Critical).

This level is set when processing cannot continue after the exception occurs.

Note that if you use Python's exception_handler() or a YPSH script's raise() with the check argument set to False, a C level exception will automatically be changed to an E level exception.

Addition of Built-in Functions
You can now change the exception level displayed in a YPSH script.

You can set this with Exception.level.set().

Changes to Language ID (ISO 639) Processing
The way language IDs are handled has been changed.
Specifically, if a language ID such as en-GB is specified and no exception description for the en-GB language ID exists, the closest possible description, such as en or en_US, will be used.
Both - and _ are supported as delimiters for language IDs.