This isn't an issue but...

Question

This isn't an issue but...

raclettes opened this issue 7 years ago · 8 comments

@william01110111 I am a C# developer (and I love this programming language). I have started developing Pinecone in C# for Windows compatibility (and you currently don't have this), with a compiler... so if I could have some sort of specification document I will happily finish it and create a pull request with the needed subfolders, code and executables (yes, so you can do stuff like C:\> pinecone myprogram.pn)

Answer 1 · 2017-04-10T17:24:08.000Z

Thanks for the interest! Windows should be supported currently. If you have any problems building it, let me know.

I'm not exactly sure what you are purposing. If you want to recreate the entire language in C#, that would be a huge undertaking I would not recommend. Now that there is a working implementation of Pinecone, the only reason it would be sensible to reimplement the language is if it was done Pinecone itself.

If you want to work on support for compiling, that would be greatly appreciated, but I would like to keep all the code in the project C++ and Pinecone unless there is a specific reason to use something else. If you wrote a compiler, would you directly generate machine code, or use a library such as LLVM? Is there a reason C# would be better for the job?

Answer 2 · 2017-04-10T20:36:38.000Z

It would be compiled to a .exe file, but it actually goes
Raw -> Lexed -> AST -> C# transpiler -> Visual Studio C# Compiler

Answer 3 · 2017-04-10T20:40:10.000Z

Also I quite like C# for readability. Again, just an ideal but if Windows support is fine then I won't bother giving myself the hassle ;-)

Answer 4 · 2017-04-10T20:41:36.000Z

I might try something like you said! Make a simple pinecone version with key usability in C#, then write higher level stuff in Pinecone.

Also is importing a thing in Pinecone?

Answer 5 · 2017-04-10T23:51:03.000Z

Ah, you want to write a transpiler from Pinecone to C#. Since I already have a Pinecone to C++ transpiler, this should not be necessary. Import is currently supported, as explained here.

Answer 6 · 2017-04-11T07:12:19.000Z

Could be for C# and C++ compatibility... that would look nice.

Answer 7 · 2017-04-11T08:34:28.000Z

If windows support is ok you need to update your readme in the upcoming features section.

Answer 8 · 2017-04-11T16:47:59.000Z

Right you are. Will do.