Skip to content

Purpose of #define SHARED_PTR? #17

@Stinkfist0

Description

@Stinkfist0

I was thinking of looking into OS X and/or Clang support in the near future. The codebase seems good with the exception TR1 (now part of C++11) features shared_ptr (and array) inclusion juggling between Boost, MSVC, and GCC TR1 implementations. As Boost is a mandatory requirement, all of this seems quite unnecessary. On a related noted, there would a small optimization opportunity by using make_shared for shared_ptr allocations throughout the codebase.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions