<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>00000cam a22000004i 4500</leader>
  <controlfield tag="001">UP-1685523046126283956</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20140806165947.0</controlfield>
  <controlfield tag="006">m    |o  d |      </controlfield>
  <controlfield tag="007">cr |||||||||||</controlfield>
  <controlfield tag="008">140806s2001    xx     d     r    |||| u|</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">0201749629 (pbk. : recycled paper)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">9780201749625 (pbk. : recycled paper)</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(iLib)UPMNL-00013193605</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
   <subfield code="a">CASM-27727</subfield>
   <subfield code="b">PerSimmons Books, Inc.</subfield>
   <subfield code="c">Php3,845.00</subfield>
   <subfield code="n">DPSM</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">CASM</subfield>
   <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1="0" ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
   <subfield code="a">QA 76.73 C153</subfield>
   <subfield code="b">M49 2001</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Meyers, Scott</subfield>
   <subfield code="q">(Scott Douglas)</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Effective STL</subfield>
   <subfield code="b">50 specific ways to improve your use of the standard template library</subfield>
   <subfield code="c">Scott Meyers.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="a">Boston</subfield>
   <subfield code="b">Addison-Wesley</subfield>
   <subfield code="c">c2001.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">xviii, 260 pages</subfield>
   <subfield code="c">24 cm.</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">unmediated</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">volume</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="490" ind1="1" ind2=" ">
   <subfield code="a">Addison-Wesley professional computing series.</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
   <subfield code="a">Includes bibliographical references (p. [225]-228) and index.</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
   <subfield code="g">Ch. 1.</subfield>
   <subfield code="t">Containers.</subfield>
   <subfield code="g">Item 1.</subfield>
   <subfield code="t">Choose your containers with care.</subfield>
   <subfield code="g">Item 2.</subfield>
   <subfield code="t">Beware the illusion of container-independent code.</subfield>
   <subfield code="g">Item 3.</subfield>
   <subfield code="t">Make copying cheap and correct for objects in containers.</subfield>
   <subfield code="g">Item 4.</subfield>
   <subfield code="t">Call empty instead of checking size() against zero.</subfield>
   <subfield code="g">Item 5.</subfield>
   <subfield code="t">Prefer range member functions to their single-element counterparts.</subfield>
   <subfield code="g">Item 6.</subfield>
   <subfield code="t">Be alert for C++'s most vexing parse.</subfield>
   <subfield code="g">Item 7.</subfield>
   <subfield code="t">When using containers of newed pointers, remember to delete the pointers before the container is destroyed.</subfield>
   <subfield code="g">Item 8.</subfield>
   <subfield code="t">Never create containers of autopt?rs.</subfield>
   <subfield code="g">Item 9.</subfield>
   <subfield code="t">Choose carefully among erasing options.</subfield>
   <subfield code="g">Item 10.</subfield>
   <subfield code="t">Be aware of allocator conventions and restrictions.</subfield>
   <subfield code="g">Item 11.</subfield>
   <subfield code="t">Understand the legitimate uses of custom allocators.</subfield>
  </datafield>
  <datafield tag="520" ind1="8" ind2=" ">
   <subfield code="a">&quot;This is Effective C++ volume three --it's really that good.&quot;--Herb Sutter, independent consultant and secretary of the ISO/ANSI C++ standards committee &quot;There are very few books which all C++ programmers must have. Add Effective STL to that list -- Thomas Becker, Senior Software Engineer, Zephyr Associates, Inc., and columnist, C/C++ Users Journal. C++ Standard Template Library is revolutionary, but learning to use it well has always been a challenge. Until now. In this book, best-selling author Scott Meyers Effective C++, and More Effective C+ reveals the critical rules of thumb employed by the experts - the things they almost always do or almost always avoid doing - to get the most out of the library. Other books describe the STL Effective STL shows you how to use it. Each of the book's 50 guidelines is backed by Meyer's legendary analysis and incisive examples, so you'll learn not only what to do, but also when to do it - and why. Highlights of Effective STL include: advice on choosing among standard STL containers (like vector and list), nonstandard STL containers (like hash_set and hash_map), and non-STL containers (like bitset). Techniques to maximize the efficiency of the STL and the programs that use it. Insights into the behavior of iterators, function objects, and allocators, including things you should not do. Guidance for the proper use of algorithms and member functions whose names are the same (e.g., find), but whose actions differ in subtle (but important) ways. Discussions of potential portability problems, including straightforward ways to avoid them. Effective STL is filled with proven wisdom that comes only from experience. Its clear, concise, penetrating style makes it an essential resource for every STL programmer.</subfield>
  </datafield>
  <datafield tag="541" ind1=" " ind2=" ">
   <subfield code="a">Php3,845.00 (PerSimmonz): Computer Science Dept.</subfield>
  </datafield>
  <datafield tag="630" ind1="0" ind2="0">
   <subfield code="a">Standard template library.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">C++ (Computer program language)</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="4">
   <subfield code="a">langage programmation.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="4">
   <subfield code="a">C++.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="4">
   <subfield code="a">STL.</subfield>
  </datafield>
  <datafield tag="830" ind1=" " ind2="0">
   <subfield code="a">Addison-Wesley professional computing series.</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FO</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPMNL</subfield>
   <subfield code="b">CASM</subfield>
   <subfield code="h">QA 76.73 C153 M49 2001</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Book</subfield>
  </datafield>
 </record>
</collection>
