Hello, Again:

I'm not making an all new computer language, please hear me out.  I'm simply against the idea of making an all new language for the Casio Prizm -- C is growing more wonderfully fun for me to code in as I delve deeper into it, and even though it's fun and all, there's not enough documentation of the Prizm to even attempt my own language for it yet.  That's why I'm moving it all to the Computer Platforms of today Specifically, windows to boot, I don't plan on getting Linux anytime soon.

Basically, it's a total movement over in platform, and few differences beside "Emerald" > "Verdant" (an unsuccessful language from the 80's already took the name Emerald, and it sounds like a total steal from Ruby) and "VixenVM" > "Vixen".

With that in mind, I'm much more open to suggestions than before, and I think I'll actually appreciate any help I can get, teaching-me-concepts and giving-advice wise.  With that in mind, I have a few areas where I would like to see some views:

- What language should I write it in?  This one will most likely turn out to be C, and that's fine, that's my idea too
- Compiled (hard), or Interpreted (Easier)?  I'm thinking Interpreted.
- OO from the bottom up like Ruby/Python, or like Java or even C++?  I'm thinking mostly OO based.
- What C compiler?  I'm not actually sure myself, I was thinking GCC, but I've heard sayings like "LLVM is faster...", so any advice on this area is welcome.
- Changes in original syntax?  I'm thinking of making it a bit more condensed.
- Changes in OOP design?  Actually, I'm sticking with the weird object groups idea I came up with most likely.
- Anything else?

I want to do it the right way from the beginning, and I think I'm able enough to do a somewhat-simple Interpreted language that could be useful in ways.  I know it won't be "Widely used throughout the industry to make Halo 5 dimensional games".

Good ideas -- I personally won't be developing for Linux though.  I know infinitely more about windows than Linux -- though with some help from other people I could eventually port it.  Though, Windows first.

Hopefully by then I have a decent chunk of the interpreter working -- I'll be glad to collaborate with you

nice perfect platform for testing a linux version.  I'll try my best to not use anything like <windows.h> so it won't be so difficult for you

And, anyone who wants to contribute ideas, feel free to post your ideal form of syntx, in a hello world program in a hello world calss

I've actually been working on this a lot lately   If you would like some stuff, it's a bit late and I don't have much time to say much, but I can give a general update:

Syntax: for now, it's actually very finalized.  It's a lot closer to a mix between Ada, Ruby, and Lua with tons of my own things
Interpreter: Haven't really started at all.
Compiler: actually, some decent progress.  Right now it detects strings, numbers, and that's all... not much, but once I get into the swing of things more, it should go faster.
Website: I need help, eventually.
Documentation: Started, far from done, but at least is almost done with operators MS Word actual has a use when you put it to work making web pages.

Now, here's an interesting part for you all.  Since I have finished the syntax for now, I am going to post 4 different examples of programs all using normal Verdant conventions.  Whoever can guess what all 4 do wins a chance to try out the Alpha compiler/interpreter and VM on August 1st.

Here they are, in order.  You get no hints from me -- I just need to see how easy they are to read and how different they are from the languages you may normally use.

1:




2:




3:




4:





Good luck

2/4 correct

yeah, it's a bit confusing, but I'm finding it to be a lot more intuitive than other languages -- plus, for your pleasure, I made the first two highly twisted

my guess is 2 tests to see if an input is "number" and 1 is an over complex hello prog

EDIT:I might be able to help with a website I learning all of that just recently