私の環境でも同様の現象を確認しました。
恐らく1つ目の方法では,AとBの設定が効かないのだと思います。
Xという仕組みでは,データを受け取ったマシンがYを実行してしまいます。
従って,まず設定 C によってデータをマシンに渡してから,AとBが実行される必要があるため
2番目の記述にしないと正しく動作しないという認識です。
しかし,この方法では私も彼と同様,バグに該当してしまうのではないかと心配しています。
私もこの点について知りたいと思っているので,どなたかコメントないでしょうか?
I think it's because in the first method, A and B is not taking effect.
With the X mechanism, the machine that receives data will execute Y.
Consequently, it's necessary to execute A and B after giving the data to the machine using the C setting,
so we need to use the second descriptor otherwise it won't operate properly.
But with this method, both me and him are worried whether it will fulfill the requirement to cause the bug.
I also want to know about this, does anyone have any comment about this?
Maybe, the first way would be that A and B setting does not work.
At the X system, the machine that got data carries out Y.
Therefore, first, by setting C, send the data to the machine and then as A and B must be executed, it will not work properly unless to make it for the second writing.
However, even with this way, I am as he is worrying it would belong to the bug.
As I also would like to know about this, is anyone commenting?