tlang
/
tlang
mirror of http://deavmi.assigned.network/git/tlang/tlang
1
0
Fork 0
Code Issues Releases Activity

Check off things already implemented 

Update test case to test them
This commit is contained in:
Tristan B. Kildaire 2021-06-06 15:54:15 +02:00
parent 3f9375c6ed
commit 70623ecd4a
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
source/tlang/testing/basic1_typedeclrationchecking.t
View File

@ -41,6 +41,11 @@ struct structTest
public int k1; public int k1;
static int k2; static int k2;
public static int k3; public static int k3;
public int g()
{
}
} }
class Shekshi class Shekshi

9
todo1.md
View File

@ -2,14 +2,15 @@ TODO: Holidays (1-10th May)
=========================== ===========================
- [ ] `parseStruct` - [ ] `parseStruct`
- [ ] Actually parse body - [x] Actually parse body
- [ ] Only allow variables declarations - [x] Only allow variables declarations
- [ ] Allow assignments I guess - [ ] Allow assignments I guess
- [ ] Maybe function definitions too (D-kinda thing) - [x] Maybe function definitions too (D-kinda thing)
- [ ] Add constructor support (initializes values) - [ ] Add constructor support (initializes values)
- [ ] I guess this is nicer when you have functions - [ ] I guess this is nicer when you have functions
in the struct too to make initialization code more modular in the struct too to make initialization code more modular
- [ ] Allow nested structs - ~~[ ] Allow nested structs~~
* Removed, why? That would be weird?
- [ ] Note to self, `parseClass` and `parseStruct` should be way more specific and not just call `parseBody` - [ ] Note to self, `parseClass` and `parseStruct` should be way more specific and not just call `parseBody`
- As currently one can then use `static` outside of these contexts - As currently one can then use `static` outside of these contexts
- [x] `parseStruct` - [x] `parseStruct`