Okay, I went and looked at a 13,848-line CSECT (lots of comments) I wrote a
couple
of years ago and there are 211 MVCs, of which eight have explicitly coded
lengths.
However, it doesn't seem like any of them would benefit from an MVC2-like macro:
MVC CvtHxBuf+1(L'CvtHxBuf-1),CvtHxBuf ...area to blanks
...
MVC StmtDbmsWhen(8),0(R1) Set external hex data from ..
MVC StmtDbmsWhen+8(8),9(R1) ... blank-separated words ...
MVC StmtDbmsWhen+16(4),18(R1) ... built by <HexConvert>
...
MVC MsgEdR1(12*4),Old.XssaR1 Copy caller's R1-R12
MVC MsgEdR14(2*4),Old.XssaR14 Copy caller's R14-R15
...
MVC UnAllWideItem+1(L'UnAllWideItem-1),UnAllWideItem
...
MVC UnOneWideItem+1(L'UnOneWideItem-1),UnOneWideItem
Again, I'm not opposed to the idea, it's just that, personally, I don't seem to
have a need for it.
--Art
At 12:12 PM 5/22/2012, Edward Jaffe wrote:
>On 5/22/2012 6:56 AM, Art Celestini wrote:
>>Personally, I have not encountered many circumstances where I needed to MVC
>>using
>>the length of the source.
>
>I find that surprising.
>
>I just scanned the assembler source code for one of our more popular products
>and found 27,930 MVCs and 927 MVC2s. That means our programmers found MVC2
>preferable to MVC in at least 3.2% of cases. These results are heavily skewed
>by
>the fact that many MVCs are found in code authored before we came up with MVC2
>some years ago.
>
>I then randomly chose one recently-coded program and found 70 MVCs and 4 MVC2s.
>MVC2 was used in 5.4% of cases or approximately one in every eighteen moves.
