Std lib vector code portable#
Std lib vector code software#

There are additional reasons that will be discussed below. Secondarily was the lack of std STL containers designed to be memory-friendly. Among game developers the most fundamental weakness is the std allocator design, and it is this weakness that was the largest contributing factor to the creation of EASTL. However, some aspects of it make it hard to use and other aspects prevent it from performing as well as it could. The large majority of the design of std STL is excellent and achieves its intended purpose. By C++ standard, we mean ISO 14882 (1998) and the 2003 update.

By STL, we mean the container, iterator, and algorithm components of the C++ standard library, hereafter referred to as std STL (with std referring to the std namespace, whereas the S in STL refers to standard C++). This document describes an STL implementation (EASTL) developed within Electronic Arts as an alternative to and extension of the STL defined by the C++ standard library.

Std lib vector code software#

The large majority of EASTL would be useful to any kind of C++ software development. This document is not a proposal, though some of EASTL's changes and extensions could form the basis for such discussions. The purpose of this document is to explain the motivation and design of EASTL so that it may help the C++ community better understand the needs of game software development. This paper describes game software development issues, perceived weaknesses of the current C++ standard, and the design of EASTL as a partial solution for these weaknesses.

Std lib vector code portable#

An extended and partially redesigned replacement (EASTL) for the C++ standard library was implemented at Electronic Arts in order to resolve these weaknesses in a portable and consistent way. Foremost among these weaknesses is the allocator model. However, weaknesses and omissions of the standard library prevent it from being ideal for high performance game software. The C++ standard library's containers, iterators, and algorithms are potentially useful for a variety of game programming needs. A result of this is that game software needs to be careful with its use of memory and the CPU. Gaming software is also faced with other limitations such as weaker processor caches, weaker CPUs, and non-default memory alignment requirements.

Most significantly, game software requires large amounts of memory but has a limited amount to work with.

Gaming platforms and game designs place requirements on game software which differ from requirements of other platforms. EASTL - Electronic Arts Standard Template Library