Hmm... I'd have to check about the "manipu-thread" (catchy, eh? ) thing and the loops-as-objects thing. I have an idea for the object one, but I'd have to wait until the compiler gets more complete to test it out

Spoiler For Profanity:

Holy shit that is a badass background!

* Freyaday wants

You can have it and others that I use here (that one is 024 out of 031)

Sometimes a while or for loop just doesn't cut it...

What about a subroutine? Or function?

Add Darl181s to this language!!!

Spoiler For what I'm talking about:

Add Gotos. What did you think I was talking about?

Hmm... Why?

Yeah, I agree now. I tried making a few sample dummy codes and I constantly typed " before ', so I'll just leave strings to be what every other programming language does. If I do implement chars, though, I'll make it similar to C# and use 's to define char literals.

Also, DERP on my part. I forgot about loops

How would having a "separate command" add confusion? C# has "null" and "void" which are essentially the same thing. The only difference (between methods and functions) is in voids, nothing is returned because it doesn't take "void" or "null" as an actual type definition.

When I was taught programming in school, I was told that a subroutine could or could not be passed any number of items and it could choose to directly modify those items or use them to modify something else within the program, and a function could or could not take arguments but returned some kind of value whose type was not null or void, but it could be null in value.
So this would be a subroutine (NOTE: in the class that I took, we used VB6; I'm just applying my learning to C#):
private void RoutineName(<any number of modifiers>) {

    //do stuff, but don't return anything

}
And this would be a function:
private <any type that's not null or void> FunctionName(<any number of modifiers>) {

    //do stuff

    return <variable that is the same type as that specified in the function definition>; //This was the key difference between a function and a subroutine; this actually returned something

}
That's what I mean when I talk about that.

I should post about my project of making a programming language...

You should.

Also...

Another thing: the subroutine thing has little point if it *takes* arguments but doesn't return anything.  The function thing is on the right path, though I think you should just stick with the function thing but call it a sub instead (so that way if you in the future decide to add real functional aspects to the language, you don't have to completely re-invent everything)

I disagree. You can have a subroutine that takes arguments yet does not return anything. Especially if you use that subroutine over and over.

For example, before I started using SharpDevelop's TextEditor, I attempted to make my own. In that, I had a subroutine called Reset, and it looked like this.
private void SetCurrent(Color highlight, int pos, int len) {

    this.SelectionStart = pos;
    this.SelectionLength = len;
    this.SelectionColor = highlight;

}

I could use that whether I was highlighting a word, or just setting the colors back to normal to resume typing.

Keeping "sub" and "<any type other than sub>" will also help with organization and readability, in my opinion.

@HOMER, if that'd be easier to help identify if vars are global or internal, sure, I'll add that. As for the other-language thing, again, nice idea. I think if I did that, though, I would probably have the other-language code be on its own page and have "#imports <file name>;" or something similar at the top.

@Ashbad, for enums, do you mean something like this?
int hello = 5;
private enum Test [[
  Times2 = hello * 2,
  Plus2 = hello + 2,
  etc.
]]
As long as the variable used to modify the values is local, I'm sure it wouldn't be too hard to implement. If I can't do that, though, would something like an enum but called a "typegroup" (name off the top of my head ) that can do that be sufficient? As for "var" I just thought that would be nice because I know that's something people who use Python really like about it. But, if it's redundant, I'll remove it. And I know classes are a must, but are namespaces?