逻辑设计模式

发布于 2024-07-15 19:14:54 字数 659 浏览 7 评论 0原文

在游戏中，许多实体应该每帧更新。我正在尝试不同的设计模式来实现这一目标。到目前为止，我已经有一个单例管理器类，每个逻辑实例都添加到其中。但我正在考虑以下内容，逻辑类本身的静态列表。这很好，因为它会从项目中删除一个类。本例中的“Engine”将是调用 update_all 的主类。

class Logic
{
public:
    Logic() { all.push_back(this); }
    virtual ~Logic() { all.erase(this); }
    virtual void update(float deltatime) = 0;

private:
    friend Engine;
    static std::list<Logic*> all;
    static void update_all(float deltatime)
    {
        for (std::list::iterator i = all.begin(); i!=all.end(); ++i)
            (*i)->update(deltatime);
    }
};

这个图案有名字吗？
您认为这是比单例管理器类更好的方法吗？
还有其他评论或警告吗？

原文

In a game, many entities should be updated every frame. Im toying with different design patterns to achieve this. Up until now, Ive had a singleton manager class to which every Logic instance is added. But Im considering the following, a static list in the Logic class itself. This is nice since it would remove a class from the project. "Engine" in this example would be the master class calling the update_all.

class Logic
{
public:
    Logic() { all.push_back(this); }
    virtual ~Logic() { all.erase(this); }
    virtual void update(float deltatime) = 0;

private:
    friend Engine;
    static std::list<Logic*> all;
    static void update_all(float deltatime)
    {
        for (std::list::iterator i = all.begin(); i!=all.end(); ++i)
            (*i)->update(deltatime);
    }
};

Does this pattern have a name?
Do you consider this a nicer approach than a singleton manager class?
Any other comments or caveats?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

欢你一世 2024-07-22 19:14:54

首先，您需要使用 remove() 而不是 erase() （后者需要一个迭代器作为参数）

如果您使用稍微不同的循环，就像

std::list<Logic*>::iterator it = all.begin();
while (it != all.end()) {
  Logic* current = *it;
  ++it;
  current->update(deltatime);
}

您甚至可以克服提到的问题siukurnin（在 update() 期间删除逻辑对象）。 list::remove() 不会使迭代器无效，除了指向已删除元素的迭代器。

除此之外，我还投票支持这是单例模式的变体。我建议将原始解决方案保留为单独的管理类，以防万一您希望拥有两个具有不同增量时间的循环或显式多线程支持（不同线程上的不同逻辑对象）或将来的任何情况。

在我看来，这是单例类相对于静态方法（您始终可以使用静态方法）的一般优势：如果您将来想这样做，您可以轻松地增加您的功能......

First, you need to use remove() instead of erase() (the latter would need an iterator as argument)

If you use a slightly different loop like

std::list<Logic*>::iterator it = all.begin();
while (it != all.end()) {
  Logic* current = *it;
  ++it;
  current->update(deltatime);
}

you can even overcome the problem siukurnin mentioned (deletion of a Logic object during update()). list::remove() doesn't invalidate iterators except of the ones pointing to the removed element.

Apart from this, I also vote for this being a variation of the singleton pattern. And I would suggest for keeping the original solution with a separate management class, just in case you want to have to have two loops with different delta times or explicit multithread support (different Logic objects on different threads) or whatever in the future.

In my opinion this is a general advantage of the singleton class over static methods (which you could always use): You can easily multiply your functionality if you want to do so in the future ...

回复收藏 0 原文