What is X++.net? - Brent Dawson - NDC London 2023

As there are so many different development languages, this is one that most may not have heard of. We'll discuss what X++ is, what it's used for and some of it's interesting features.
Check out our new channel:
NDC Clips:
‪@ndcclips‬
Check out more of our featured speakers and talks at
ndcconferences.com/
ndclondon.com/

[@user-dq7vo6dy7g]

The camera angle in combination with the seat selection of the audience is not very fortunate. Unless there was really only one person watching the talk.

[@jerkifer924]

I'm glad I looked at the comments before wasting 45 minutes.

[@TonyTigerTonyTiger]

4:26 AOT doesn't stand for Application Object Template, it stands for Application Object Tree.

[@TonyTigerTonyTiger]

11:55 It was not virtually impossible to debug X++ code in the MorphX IDE. There were newer features in Visual Studio debugging that were never moved into X++ debugging, in MorphX but all the standard features were there: breakpoints, enable/disable/delete breakpoints, a form that showed all breakpoints and if they were enabled and from which you could disable/enable multiple breakpoints at once - step into, step out, step over - various windows (locals window showed local variables and their value, a globals windows that showed global variables and their values, watch windows let you add a set of variables to them so that you did not have to dig around in the variables to find the ones you were interested in, and a stack window that showed the call stack) - and you could change the values of variables while debugging, you could move around the call stack and see the values of the variables in those method contexts, and other features. Conditional breakpoints were not available, but it takes only 2 simple lines of X++ code to mimic that behavior, so indirectly, there was also conditional breakpoints.
Again, there were some nice-to-have features that were missing, but he is vastly downplaying the debugging features in X++ in MorphX.
Also, several types of code ran as CIL, and that could be debugged with VS: so for all of that code, there was fully VS debugging.

[@TonyTigerTonyTiger]

16:00-ish He again undersells X++.
1) For your own code, you can say whatever you want in an error message. For example ...
throw error(strFmt('Serial number %1 has already been posted good for Operation %2: see Job card %3', inventSerialId, oprId, journalId));
2) He is just being childish by saying that the Retry is like a GOTO. So is the bottom of a for loop, for example. That jumps up to a single specific predefined starting place. Heck, he might as well say that any jumping around in code - as opposed to strict linear, sequential processing - is like a GOTO.

[@TonyTigerTonyTiger]

41:51 He does it again. It's like he hates X++ and keeps trying to give X++ a black eye. He says "The object oriented programming (OOP) principles of X++ differ from other languages such as C#". He then lists 5 examples.
But hold on. 2 of those ARE like C#.
- Method overriding is supported.
- Parameters can be optional and can have defaults.
So 40% of his examples are wrong.
And one could argue that his first example also fails:
- Downcasting is done via the as keyword.
The PRINCIPLE of downcasting is the same as in C#, just the way it is implemented is different.
I would say that 3 out of his 5 examples - 60% - are bogus.

[@jimmmanuel7420]

it's like this guy doesnt like X++ and doesnt really know anything, He cant even pronounce Axapta.