-
A multi-line comment would be really helpful.
It makes logical sense to use `/* Comment */`, to fit with the C style `//` comments.
Thank you.
Woccz updated
3 years ago
-
As all files compiled from nolol are optimised, perhaps the generated yolol file should be of `progName.opt.yolol` format?
Thank you.
Woccz updated
3 years ago
-
There should be a way to check if a yolol-script is using operations that are not available on the chosen chip-type.
The hard-part would be how to specify the chip-type.
The first step would proba…
-
Is there a way for VS Code NOLOL/YOLOL to prompt you to save the file before running the compiling/optimising scripts?
This isn't an urgent change, but it would be nice for quality of life if it is n…
Woccz updated
3 years ago
-
if i do cmake --build on the build directory i made i get following error:
`/home/sedrowow/Dokumente/GAMES/nolol/Include/NsCore/TypePropertyUtil.h: In Funktion »Noesis::Ptr Noesis::GetComponent(const…
-
Currently jumping to the content of a variable is (for obvious reasons) not possible in nolol. A similar feature would however be quite usefull. There should be some way to dynamically jump through co…
-
Add a include-directive that allows the inclusion of other nolol files into a file.
Should be line-oriented (= can appear as a line and inside if/while, but not as an expression or single statement…
-
Introduce a hidden variable that is automatically incremented at the beginning of every lines.
At a builtin function to retrieve the value of this variable.
It can then be used to measure time ins…
-
Give the user the ability to decide which statements belong on one line and which ones should be on seperate lines.
-
Add possibility to program line-precise in nolol.
Mainly:
1. These and only these statements belong in a single line
```
other= bla
{
all=1
this=all+1
ononeline=0
}
```
2. Specifiy dela…