My point is that from our experience, creating individual tables for
individual agents is an extraordinary case. Default arguments designed to
be used for ordinary cases. If y'all really disagree with that, then I
won't fight it.


On Thu, Feb 21, 2013 at 9:37 AM, Robert Carlsen <notifications@github.com>wrote:

> In src/Core/Utility/EventManager.h:
>
> > +    as they come.
> > +
> > +    @param count # events to buffer before flushing to backends.
> > +    */
> > +    void set_dump_count(unsigned int count);
> > +
> > +    /*!
> > +    Creates a new event for creator with title.  It uses uniquely
> > +    identifiable information from creator (e.g. ID) to create a unique
> > +    namespaces for related events.
> > +
> > +    @param creator the agent that created this event @param title a
> > +    label to distinguish event sets from other sets from the same
> > +    creator.
> > +    */
> > +    event_ptr newEvent(Model* creator, std::string title);
>
> There are definitely good uses for both cases. With several agents each
> creating their own tables, however, I don't think we should have to worry
> about agent developers potentially having given their tables conflicting
> names. They still have the ability to opt-out of namespacing via passing
> NULL, but I think it is "safer" to keep that explicit - in the hopes that
> it will help them recognize that their event title selection should be done
> more carefully. I probably should discuss the NULL option in the doc
> comments. Sound reasonable?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cyclus/cyclus/pull/456/files#r3100376>.
>
>