Releases: Elemnto56/Intextual_File_Language
Bugs Fixes of Logic
Intext v0.8.1
After noticing some major bugs in the last release, I decided to release this patch. One that not only addresses the previous bugs, but also introduces new features and QOLs improvements.
Fixes:
- If statements would run even if the logic was false; this was fixed
- Others that I long had forgeten
Improvements and Additions:
- Macro declaration
macro . greet() {
output "Hello World"
}
- Shorthand variable declaration
x = "Hello World"
- Improved mathematics and concat
- Many more!
Notes
Most of this info will be included in the docs.
"But you barely update the docs..."
Well, I'm the only person working on this, so be patient.
Intext is still in development so don't expect something as top notch as Python
Where's The Logic?
Intext v0.8 – Where is the logic?
After nearly two months in the lab, Intext finally gets its long-awaited logic upgrade. This release introduces full support for logic control, paving the way for actual programming-style behavior beyond simple file output. While Intext is still fundamentally a file/text automation language, this version adds just enough "brain" to start thinking for itself.
What's New ?
-
if / else if / or if / else - The standards. Nothing different from other languages.
-
while loops – Repeats as long as a condition holds true.
-
repeat loops – Count-based iteration with optional iterator variable.
-
stop / skip – Break and continue for loop control (aliases for break and continue; you can still use break and continue tho).
-
Text blocks – Multi-line string support using [[[ ... ]]].
-
Expression reassignment – Support for x += 1, x *= 2, etc. BUT NOT:
x = y + 2or anything similar -
Internal enhancements – Nested logic parsing fixes, cleaner interpreter loop handling, and an overall more durable ISEC.
Notes
-
Function calls in expressions are limited, especially for unpredictable ones like read(), which are only valid in declared variables. So, for example, you can do
let x: string = read(...), but notoutput read(...) -
When a script is ran, Intext will create a
.intextdirectory and acache/directory within the.intextdirectory. So, make sure you don't have any security settings that would block this behavior.
- If you have an issue, create an issue in the "Issues" tab.
- For docs go to https://docs.codekeg.dev