Discussions on more advanced topics such as monolithic vs micro-kernels, transactional memory models, and paging vs segmentation should go here. Use this forum to expand and improve the wiki!
SpyderTL wrote:Old guys can keep using ASM. It's not like I'm taking it away.
You have proposed a language, I have suggested that it can be better. Why we should talk about guys using assembler?
SpyderTL wrote:But the XSLT files can't run themselves, just like .s files can't run themselves, or .java files can't run themselves.
Java files can run themselves. My system (written in Java) writes OS image and the image runs Java classes. No help from anything else except file manager to copy image on a flash. But copying is still possible to implement in Java. That's why I repeat my thoughts about "pure" XML system.
SpyderTL wrote:Old guys can keep using ASM. It's not like I'm taking it away.
You have proposed a language, I have suggested that it can be better. Why we should talk about guys using assembler?
SpyderTL wrote:But the XSLT files can't run themselves, just like .s files can't run themselves, or .java files can't run themselves.
Java files can run themselves. My system (written in Java) writes OS image and the image runs Java classes. No help from anything else except file manager to copy image on a flash. But copying is still possible to implement in Java. That's why I repeat my thoughts about "pure" XML system.
I definately like your approach better than mine, but your java files still need a "compiler". In your case, your compiler is written in Java. Mine is written in C#.
What you are saying is that I should write an XML compiler in XML. That's kind of like saying that I should write a web browser in HTML. XSLT is great for transforming XML files from one schema to another, but it's terrible as a programming language.
Java definately would have been a better choice.
Actually, to be honest, my first attempt was using C# instead of XML. I just didn't think of writing a C# compiler in C#. That would have been brillient!
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
SpyderTL wrote:What you are saying is that I should write an XML compiler in XML. That's kind of like saying that I should write a web browser in HTML. XSLT is great for transforming XML files from one schema to another, but it's terrible as a programming language.
But wait, aren't you going to write OS in XML? OS has a lot of complex algorithms and if it is written in XML, then you just must to have a great experience of writing complex algorithms in XSLT. Then what is the problem with a compiler? And one more point - if you was talking about XML as internal data format of your OS, then there should be some parser and some internal structured representation, but what prevents you from using all of that and to write a transformation from internal representation to hex stream?
