I guess I should note that G65 in this case is not a macrocall, but a "non movement".. basically what it does is it allows you to eliminate the need for a prep move prior to moving to your start position so that cutter comp is properly initiated, it eliminates the "jumping" that can occur. As im sure you all know the compensation is calculated based on the previous point, the current point and the next point.. if I just moved to x0y0, then the comp would kick in on the first circular interpolation and could cause problems when the machine "jumps" into the comped position such as ramming into the part etc.. So basically G65 gives the machine a 'previous' position to work with, even though no movement was made.. its pretty clever if you ask me.
Ive been a programmer all of my life, html, css, php, c, c++, visual basic, etc.. it goes on and on. Correct syntax is very important to me, as is elimating redundancy.. I cant stand the mentality of some people of "if it works its good enough, who cares if I dont understand why it works".