Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks.
For the bigger picture, a debugger may really be helpful, an external community emulator maybe useful, but it requires a lot of time to setup the device statuses.
For coding level, I guess:
- line limits, e.g.: comment lines should not be counted as line, it's simple to remove in the preprocessing, and because of this, relative jump may need to re-think, maybe comments line should not be numbered.
- The new machine instructions are nice addons but lacks documentations.
- No counterparty for function peek.
- Variable name should support underline.
- No sbns.
- Could add some simple conditional operations like treat >=0 like 2 or 3 or etc all count as positive, e.g.: sand a b c, if both b and c >=0, then set a to 1.
- Could add deeper call stack tracking, rather than single ra.
- Could add more stack, lol, so we may emulate array, map, etc.
I guess that's too much, you see what's fit.