What's up with this semicolon?

re: What's up with this semicolon?

Petur Snaeland — Mon, 28 Apr 2008 18:26:08 GMT

Big news! I for one never bought the explanations that this was necessary. Actually, since Axapta 2.1 I never had that problem because I grew up in C/C++ and chose to use descriptive variable names like "AccountNum nextCustomerId;" in X++, which happens to avoid the issue altogether AND leaves more readable code. I hope your good colleagues will bring this out in the next AX4 and AX3 service packs too. Great initiative Michael.

re: What's up with this semicolon?

dewetha — Mon, 28 Apr 2008 22:06:25 GMT

hopefully this makes the suppose best practice of placing a semi colon in methods above any code. including one without type declarations.

i.e. best practice?:

int addTwo( int _in)

{

;

return _in + 2;

}

now can be:

int addTwo( int _in)

{

return _in + 2;

}

that will make teh confilct betwenn an accepted best practice and MBS layers the same.

re: What's up with this semicolon?

Strider — Tue, 29 Apr 2008 12:14:49 GMT

I've allways hated the practice of naming variables after their type using camel casing. You may argue that C/C++ developers have been doing this for ages, but C is case sensitive. X++ is not!

I strongly beleive that variable names should describe their content and semantics and not their type. It makes code much more readable for human beings!

It's a qood thing the semicolon is no longer necessary but apart from that you should really reconsider some of the X++ "best practices"!

re: What's up with this semicolon?

Martin Olsson — Tue, 29 Apr 2008 12:32:07 GMT

Great work! I really really appreciate that you took the time to fix this.

re: What's up with this semicolon?

dewetha — Tue, 29 Apr 2008 14:12:15 GMT

I like that fact that x++ is case insensitive. really, how big does a method/funtion need to be to have to start reusing names?

I would like to see the old VB functionality that if I declare a variable and then in code,type it in lower case. it will then format it for me to what I declared. that is awesome for use guys that are lazy typists!

i.e. declare:

int FooBar;

type: foobar = -1;

compile makes it: FooBar = -1;

since you are the GURU ;)

re: What's up with this semicolon?

mfp — Wed, 30 Apr 2008 09:29:37 GMT

The best practice in X++ for naming of variables can be seen here:

http://msdn.microsoft.com/en-us/library/aa892904.aspx

As can be read here, variables should always be named logically, ie. the name should describe the contents in the variable.

However, as EDTs are also named logically there often are clashes. Sometimes a variable is just an accountnum, and then you shouldn't make up variable names like _accountNum, myAccountNum, etc.

Regardless of how you name your variables the dangling semi-colon can still be an annoyance in methods without any variable declarations.

void helloWorld()

{

;

info("Hello World");

}

first command is static ??

Sebastian Draese — Sat, 23 Aug 2008 23:42:20 GMT

the dangling semicolon is also needed,

when the first command is an static-method call,

void test()

{

; // <--- you'll need this, because info() -> global::info()

info("test");

}

re: What's up with this semicolon?

Rakesh — Wed, 07 Jan 2009 10:04:32 GMT

I come to AX from C# background and had always cursed X++ for the dangling semi-colon. Great to know that it won't be required in near future.

re: What's up with this semicolon?

Carl S — Mon, 30 Nov 2009 13:00:29 GMT

Sunday morning, so boring, what can I do...

Ah! let's have a look at AX and make some changes in the X++ grammar...