Does it make sense to dissect design in this way or should we just accept the fact that everything is intertwined and come up with a reasonable way to discuss and describe it?
以这种方式来剖析设计有意义吗?或者我们应该接受一个现实:物与物之间都是由联系的,应该用一种更合理的方式来讨论和描述。
Porting legacy, untested code in Perl or any language is just plain tough, but writing failing tests could be a great help, and are a reasonable strategy.
移植未经测试的遗留perl或其他语言代码的确非常困难,但编写失败测试可能会帮上大忙,是一个合理的策略。
Ten elements to do what any reasonable XML format can accomplish in four or five (and just six elements in plain HTML).
十个元素所完成的任务对于任何合理的xml格式来说只需四个或五个元素就够了(无格式的HTML中也只需六个元素)。
It's reasonable because it's meant TMP for temporary purposes just to call it temp or T-M-P for short, X and I can define temp as -- why don't I set it as equal to X, initially, because now that I've stored X in a separate chunk of memory, I can now change its value and then I can say Y gets, not X, but temp, and so now I've actually swapped these values.
这是合理的,因为它是为,暂时的目的,只要叫它Temp或简称它为,我可以定义temp为--为什么我不把它设定为等于,最初的,因为现在我把X存储在一个单独的内存块中,我现在可以改变它的值,然后我说Y等于,不是X,而是temp,所以现在我交换这些值。
应用推荐