|
|
|
|
|
|
by kreco
2239 days ago
|
|
|
Sorry I won't be able to give you a lot of feedback. As a matter or preference I really like colons and semi-colons. That said your work is amazing. This is a true example of simplicity. I don't think most of people would get how difficult it is to keep it simple. Everything is clear I can read the source code without asking myself "what is that", everything makes sense. Thanks for presenting your work. Do you have any constraints, like "no meta programming", "generated
library should be as much as possible compatible with C", "it should have one pass optimization" or even "the compiler must be embeddable in most place as possible" ? |
|
|
Thanks for saying all that. It was a huge amount of work and getting appreciation makes it all worth it!
No hard constraints as of now. But I don't think I want to include meta programming or a pre-processor (don't really like it to be honest). I do want to keep it compatible with C internally, on Assembly level. One thought is, to create a file with function headers/definitions that are then dynamically linked and can just be used.
I used some C std library functions that way for debugging (printf, ...). And as I follow the standard calling conventions, the compiler should automatically generate compatible code.
With this, it would also be possible, to write OpenGL code. That would be really awesome :)
As of usage of my language - Not sure yet. Up until now, the road was more of the goal then the finished language.