| Topic List | Page List: 1 |
|---|---|
| Topic | Ok, college is a joke. |
| Yellow 06/01/19 11:47:06 PM #17: | Sahuagin posted... well, it might not be that hard to *start* writing a C# interpreter (in C#). but like, good luck with type inference and generics and covariance, etc.etc. I have myself written an interpreter, but only by using an extremely constrained language and syntax. writing an interpreter for a general-purpose language is no small feat. I'd probably just use a lot of reflection to replicate the code running on the actual framework running underneath. For storing data, I'd probably do a hashtable[Type] of hashtable[index]. It wouldn't be perfect, but I'd be able to get an XNA game playing at full speed. It would be kind of cool, but ultimately completely useless and a waste of time. Getting an interpreter on another OS/Architecture? That would be hard. That would be Wine levels of work, or at least, it would have to use Wine. I've written a very crappy C++ interpreter and enough of an NES emulator to get the gist of how emulators/interpreters really work. I've already done a ton of work generating C# code out of objects and generics and things like that with my object to child class converter. That's something I'm actually proud of. And no, I really don't understand JavaScript, but my definition of "basically the same thing" is more, "relative to SQL and HTML, JavaScript is basically C#, and should be very easy to learn" --- ... Copied to Clipboard! |
| Topic List | Page List: 1 |