[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fK0_uSMWTlxiArMsdhyl6Bqif_07HDvM35_1Nj57w8tw":3},{"answer":4,"createTime":5,"id":6,"options":7,"origin":12,"question":16,"related":17,"source":27,"type":28},[],"2023-12-21 12:34:50",118865115,[8,9,10,11],"实现撤销(Undo)操作和恢复(Redo)操作","将请求的发送者和接收者解耦","不改变聚合类的前提下定义作用于聚合中元素的新操作","不同的时间指定请求,并将请求排队",{"courseId":13,"courseImg":14,"courseName":15},"812c1baf8bb3c96a121e5b93dd1b24b5","https:\u002F\u002Ftihai-oss-cloud.itihey.com\u002Fimg\u002F25b30343053994e8940089572d36015b.jpg","设计模式","在( )时无须使用命令模式",[18,29,38,47,50,59,68,77,87,96],{"answer":19,"createTime":5,"id":20,"options":21,"question":26,"source":27,"type":28},[],118865108,[22,23,24,25],"动态决定由一组对象中某个对象处理该请求","动态指定处理一个请求的对象集合,并高效率地处理一个请求","使多个对象都有机会处理请求,避免请求的发送者和接收者间的耦合关系","将对象连成一条链,并沿着该链传递请求","下图描述了一种设计模式,该设计模式不可以( ).\u003Cimg src=\"https:\u002F\u002Ftihai-oss-cloud.itihey.com\u002Fimg\u002F9363dfa7c509015d1c023fb025770a2a.png\">","v1",0,{"answer":30,"createTime":5,"id":31,"options":32,"question":37,"source":27,"type":28},[],118865112,[33,34,35,36],"职责链 (Chain of Responsibility)","命令 (Command)","备忘录 (Memento)","工厂方法 (Factory Method)","接力赛跑体现了( )设计模式",{"answer":39,"createTime":5,"id":40,"options":41,"question":46,"source":27,"type":28},[],118865114,[42,43,44,45],"命令模式将一个请求封装为一个对象,从而使我们可用不同的请求对客户进行参数化","命令模式可以将请求发送者和请求接收者解耦","使用命令模式会导致某些系统有过多的具体命令类,导致在有些系统中命令模式变得不切实际","命令模式是对命令的封装,命令模式把发出命令的责任和执行命令的责任集中在同一个类中,委派给统一的类来进行处理","以下关于命令模式的叙述错误的是( )",{"answer":48,"createTime":5,"id":6,"options":49,"question":16,"source":27,"type":28},[],[8,9,10,11],{"answer":51,"createTime":5,"id":52,"options":53,"question":58,"source":27,"type":28},[],118865116,[54,55,56,57],"当一个待解释的语言中的句子可以表示为一颗抽象语法树时,可以使用解释器模式","在解释器模式中使用类来表示文法规则,可以方便地改变或者扩展文法","解释器模式既适用于文法简单的小语言,也适用于文法非常复杂的语言解析","需要自定义一个小语言,如一些简单的控制指令时,可以考虑使用解释器模式","关于解释器模式,以下叙述有误的是( )",{"answer":60,"createTime":5,"id":61,"options":62,"question":67,"source":27,"type":28},[],118865117,[63,64,65,66],"组合 (Composite)","适配器 (Adapter)","中介者 (Mediator)","状态 (State)","在图形界面系统开发中,如果界面组件之间存在较为复杂的相互调用关系,为了降低界面组件之间的耦合度,让它们不产生直接的相互引用,可以使用( )设计模式",{"answer":69,"createTime":5,"id":70,"options":71,"question":76,"source":27,"type":28},[],118865119,[72,73,74,75],"迭代器模式提供一种方法来访问聚合对象,而无须暴露这个对象的内部表示","迭代器模式支持以不同的方式遍历一个聚合对象","迭代器模式定义了一个访问聚合元素的接口,并且可以跟踪当前遍历的元素,了解哪些元素已经遍历过而哪些没有","在抽象聚合类中定义了访问和遍历元素的方法并在具体聚合类中实现这些方法","以下关于迭代器模式的叙述错误的是( )",{"answer":78,"createTime":79,"id":80,"options":81,"question":86,"source":27,"type":28},[],"2023-12-21 12:34:51",118865120,[82,83,84,85],"抽象","聚集","单例","共享","迭代器模式用于处理具有( )性质的类",{"answer":88,"createTime":79,"id":89,"options":90,"question":95,"source":27,"type":28},[],118865124,[91,92,93,94],"迪米特法则","接口隔离原则","里氏代换原则","合成复用原则","中介者模式中通过中介者来将同事类解耦,这是( )的具体应用",{"answer":97,"createTime":79,"id":98,"options":99,"question":104,"source":27,"type":28},[],118865126,[100,101,102,103],"中介者模式用一个中介对象来封装一系列的对象交互","中介者模式与观察者模式均可以用于降低系统的耦合度,中介者模式用于处理对象之间一对多的调用关系,而观察者模式用于处理多对多的调用关系","中介者模式简化了对象之间的交互,将原本难以理解的网状结构转换成相对简单的星型结构","中介者将原本分布于多个对象间的行为集中在一起,改变这些行为只需生成新的中介者子类即可,这使各个同事类可被重用","以下关于中介者模式的叙述错误的是( )"]