Comments on: The X++ way to getters and setters http://sysdictcoder.com/blog/the-x-way-to-getters-and-setters/ Dynamics Ax stuff Fri, 30 Apr 2010 19:01:01 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Björn http://sysdictcoder.com/blog/the-x-way-to-getters-and-setters/comment-page-1/#comment-21 Björn Tue, 17 Jul 2007 18:43:51 +0000 http://sysdictcoder.com/blog/the-x-way-to-getters-and-setters/#comment-21 Good point, SebDra. Big data types require special care, but these situations are quite rare. Even in the standard code prmIsDefault() is not very common in a parm-method. It makes me wonder how bad performance is with an extra function call for "simple" data types. Maybe that's something for another post. Good point, SebDra. Big data types require special care, but these situations are quite rare. Even in the standard code prmIsDefault() is not very common in a parm-method. It makes me wonder how bad performance is with an extra function call for “simple” data types. Maybe that’s something for another post.

]]> By: SebDra http://sysdictcoder.com/blog/the-x-way-to-getters-and-setters/comment-page-1/#comment-20 SebDra Tue, 17 Jul 2007 06:32:40 +0000 http://sysdictcoder.com/blog/the-x-way-to-getters-and-setters/#comment-20 yes, but every extendeddatatype will transferred "by-value", so be carefull with big containers or arrays. "best practice" is: use the x++ function prmisdefault() CustAccount parmCustAccount(CustAccount _custAccount = "") { ; if ( ! prmisdefault( _custAccount )) custAccount = _custAccount; return custAccount; } yes, but every extendeddatatype will transferred “by-value”,
so be carefull with big containers or arrays.

“best practice” is: use the x++ function prmisdefault()
CustAccount parmCustAccount(CustAccount _custAccount = “”)
{
;
if ( ! prmisdefault( _custAccount ))
custAccount = _custAccount;

return custAccount;
}

]]>