where is the definition?

[Jim Z. Shi]

hi, all
i looked through <stl_deque.hfor some reason, but i can not find the
definition of the method `erase()', there are just two declaration:
//----------------------------------
iterator
erase(iterator __first, iterator __last);

iterator
erase(iterator __position);
//----------------------------------

where is the definition?

thanks,
Jim

[Tonni Tielens]

On Sep 23, 11:53*am, "Jim Z. Shi" <[e-mail]:

where is the definition?

Depends on the compiler. The definition can be in a precompiled
library or in a seperate source file.

[James Kanze]

On Sep 23, 3:44 pm, Tonni Tielens <[e-mail]:

On Sep 23, 11:53 am, "Jim Z. Shi" <[e-mail]:

where is the definition?

Depends on the compiler. The definition can be in a
precompiled library or in a seperate source file.

Or built into the compiler, or in a database somewhere, or
whatever the implementation wants. The name of the file he gave
reminds me of g++, however, where the standard library is in
files, with most of the actual code in a sub-directory bits,
with the class definitions and inline functions in .h files and
the template implementations in .tcc files. If the original
poster is asking about g++, given that there is a file
bits/deque.tcc, that's where I'd look.

More generally, if I want to find out about the actual contents
of a header, I'll write a one line program which includes it;
most compilers have an option which will generate the
preprocessor output (usually -E or /E), which will contain the
code (with all macros expanded) and #line declarations
specifying where it comes from.

--
James Kanze (GABI Software) email:ja*********@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]

[Jim Z. Shi]

James Kanze wrote:

On Sep 23, 3:44 pm, Tonni Tielens <[e-mail]:

>On Sep 23, 11:53 am, "Jim Z. Shi" <[e-mail]:

More generally, if I want to find out about the actual contents
of a header, I'll write a one line program which includes it;
most compilers have an option which will generate the
preprocessor output (usually -E or /E), which will contain the
code (with all macros expanded) and #line declarations
specifying where it comes from.

:)

this helps a lot.

thanks,
Jim