Discussion New Language - Discussion

[ertaboy356b]

Please leave scope alone..

 

[Lyerae]

Officially working on this now. Currently typing up the definition (basically, what the language has and how it works.) at the moment.

Questions though.
Public or pub keyword?
Private or priv keyword?
Anyone care if I eliminate scopes, and make it 100% library-based?
Does anyone have a better name for libraries!?
Start/end blocks, or { } blocks?
C-Like function declarations (return-type name(arguments...)), or normal JASS-Type declarations (I can do any other kind if anyone wants. As long as people agree on it. I just think that C-Like functions are cool, but that's my personal opinion)?

 

[GetTriggerUnit-]

| is or.

Perhaps something like ~ or \

But I don't see the need for that.

Isn't it || or, && and?

-----

private
public
100%
library->class
{}
public int hello() {}

 

[Darthfett]

public or [del]pub[/del] keyword?
private or [del]priv[/del] keyword?

Anyone care if I eliminate scopes, and make it 100% library-based?

Please do that. Scopes are lame.

Does anyone have a better name for libraries!?

I prefer the term 'library'. 'package' if you must change it.

Start/end blocks, or { } blocks?

I like both for different reasons.

C-Like function declarations (return-type name(arguments...)), or normal JASS-Type declarations (I can do any other kind if anyone wants. As long as people agree on it. I just think that C-Like functions are cool, but that's my personal opinion)?

I like C-like declarations, but I find the 'void' keyword to be lame.

 

[Lyerae]

> class

I'm planning on a class-type already.

> void' keyword to be lame.

I was going to use null.

 

[Sevion]

Isn't it || or, && and?

Trufax, but it would be confusing if | had both functions.

 

[GetTriggerUnit-]

null or void is the same.

If you put none, it looks like the class' initialization. (fail )

Rather keep void or null or function.

----

Trufax, but it would be confusing if | had both functions.

Yea* my bad
(the * points my idiocy located into my retarded memory. :O)

----

Maybe an easy way to debug the codes such as:
debug << "C style"; (debugging only)
becomes call BJDebugMsg("Jass style");

 

[Darthfett]

Maybe an easy way to debug the codes such as:
debug << "C style"; (debugging only)
becomes call BJDebugMsg("Jass style");

The << operators are ugly, if anything you should just use something like:

print "message"

or

print("message")

 

[Narks]

What is wrong with scopes?

 

[Sevion]

The << operators are ugly, if anything you should just use something like:

print "message"

or

print("message")

I second this.

> What is wrong with scopes?

Scopes are non-standard. Libraries, Structs, and Classes are more standard.

 

[Nestharus]

use namespace instead of library : \

use class keyword when dealing with vars+methods
struct keyword for vars only

Really, it should all be struct though, unless you plan on using a hashtable implementation for classes, which I seriously don't suggest ^_^.

>print("message")
No, use printf...


Furthermore, allow access to the lexical environment

Provide common things like collections and heaps

 

[GetTriggerUnit-]

if (value > 0) {
    return 100;
} else {
    return -100;
}

return (value > 0) ? 100 : -100;

Implementing this would be awesome.

http://java.sun.com/docs/codeconv/html/CodeConventions.doc9.html#353

 

[Jesus4Lyf]

If there are any {} in this language, I assure you I would rather code with vanilla JASS.

Edit: By the time the page showed up after writing this post, the post below had been added. Hot thread...

 

[Lyerae]

You know, the more features I implement, the longer it takes to create.
It'll be awhile before I get everything working correctly.

> use namespace instead of library : \

I think I like namespace.

> allow access to the lexical environment

Explain?

 

[GetTriggerUnit-]

You know, the more features I implement, the longer it takes to create.
It'll be awhile before I get everything working correctly.

Actually, you should just do the compiler. I'd like, if you want, to do an IDE for your compiler.

 

[Lyerae]

> If there are any {} in this language, I assure you I would rather code with vanilla JASS.

Why?

> Actually, you should just do the compiler. I'd like, if you want, to do an IDE for your compiler.

I'm not quite sure I understand what you mean...

 

[Darthfett]

If there are any {} in this language, I assure you I would rather code with vanilla JASS.

I may have agreed with you on this point in the past, but I think that since these sorts of blocks are so widely used in actual coding languages, it might be better to use them, in order to make veteran coders (who are new to JASS) able to adapt quickly, as well as make veteran JASSers (people who become familiar with this language) able to switch to other languages.

use namespace instead of library : \

namespace is uglier than library and package.

>print("message")
No, use printf...

...No. Use print. Why add an extra random letter on it?

Actually, you should just do the compiler. I'd like, if you want, to do an IDE for your compiler.

I would also like it if the compiler was independent of the IDE.

 

[GetTriggerUnit-]

Well, here's a simple comparison.

IDE what you developp in. -- Trigger Editor
Compiler what turns your code into readable Jass.(what ever language is used) -- Jasshelper

Like... Let's say C++ (but that must be do-able in python too)

int main(int argc, char *argv[])
{
    // argv[0] could be the in file
    // argv[1] could be the out file
}

In my IDE that I would do in Java, I'd call your Compiler

String[] cmd = new String[3];
cmd[0] = "compiler.exe"; // program
cmd[1] = "in.j"; // input file
cmd[2] = "out.j"; // output file
Runtime.getRuntime().exec(cmd); // execute compiler
// Then done.

 

[Nestharus]

>...No. Use print. Why add an extra random letter on it?

print format...

>namespace is uglier than library and package.

Not at all.. namespace is a standard used by many languages...

>lexical environment
After processing static text into the lexical crap (lines, structures, etc), let scripting languages access that huge structure for manipulation, like changing what lines are, adding new lines, copying structures, etc.

>Why?
Lye lye, keep it close to JASS... follow JASS syntax like vjass does. You could do a C Style syntax and what not, but keep it in its own block. Only things that should compile plainly are things in JASS style syntax.

So as not to *100% break* older resources, follow current vjass conventions for the current features. You could add on and what not, but the current features should stay supported.

If you were doing 100% entirely dif, then put it in its own language block and go all out.

My suggestion: get vexorian to put the compiler he's working on out so you can fix up vjass and write your own language or w/e (with custom syntax) with its own language block need be.

http://www.wc3c.net/showpost.php?p=1120197&postcount=1775

Please do the right thing ><.

 

[Lyerae]

> My suggestion: get vexorian to put the compiler he's working on out so you can fix up vjass and write your own language or w/e (with custom syntax) with its own language block need be.

Do you mean fix JassHelper, or get him to release the new one he's working on, and add it to that?