JavaPerformance/JavaPerformance/data/data-small.txt at master · plusterkopp/JavaPerformance

Repository navigation

History

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409

410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441

442

443

444

445

446

447

448

449

450

451

452

453

454

455

456

457

458

459

460

461

462

463

464

465

466

467

468

469

470

471

472

473

474

475

476

477

478

479

480

481

482

483

484

485

486

487

488

489

490

491

492

493

494

495

496

497

498

499

500

501

502

503

504

505

506

507

508

509

510

511

512

513

514

515

516

517

518

519

520

521

522

523

524

525

526

527

528

529

530

531

532

533

534

535

536

537

538

539

540

541

542

543

544

545

546

547

548

549

550

551

552

553

554

555

556

557

558

559

560

561

562

563

564

565

566

567

568

569

570

571

572

573

574

575

576

577

578

579

580

581

582

583

584

585

586

587

588

589

590

591

592

593

594

595

596

597

598

599

600

601

602

603

604

605

606

607

608

609

610

611

612

613

614

615

616

617

618

619

620

621

622

623

624

625

626

627

628

629

630

631

632

633

634

635

636

637

638

639

640

641

642

643

644

645

646

647

648

649

650

651

652

653

654

655

656

657

658

659

660

661

662

663

664

665

666

667

668

669

670

671

672

673

674

675

676

677

678

679

680

681

682

683

684

685

686

687

688

689

690

691

692

693

694

695

696

697

698

699

700

701

702

703

704

705

706

707

708

709

710

711

712

713

714

715

716

717

718

719

720

721

722

723

724

725

726

727

728

729

730

731

732

733

734

735

736

737

738

739

740

741

742

743

744

745

746

747

748

749

750

751

752

753

754

755

756

757

758

759

760

761

762

763

764

765

766

767

768

769

770

771

772

773

774

775

776

777

778

779

780

781

782

783

784

785

786

787

788

789

790

791

792

793

794

795

796

797

798

799

800

801

802

803

804

805

806

807

808

809

810

811

812

813

814

815

816

817

818

819

820

821

822

823

824

825

826

827

828

829

830

831

832

833

834

835

836

837

838

839

840

841

842

843

844

845

846

847

848

849

850

851

852

853

854

855

856

857

858

859

860

861

862

863

864

865

866

867

868

869

870

871

872

873

874

875

876

877

878

879

880

881

882

883

884

885

886

887

888

889

890

891

892

893

894

895

896

897

898

899

900

901

902

903

904

905

906

907

908

909

910

911

912

913

914

915

916

917

918

919

920

921

922

923

924

925

926

927

928

929

930

931

932

933

934

935

936

937

938

939

940

941

942

943

944

945

946

947

948

949

950

951

952

953

954

955

956

957

958

959

960

961

962

963

964

965

966

967

968

969

970

971

972

973

974

975

976

977

978

979

980

981

982

983

984

985

986

987

988

989

990

991

992

993

994

995

996

997

998

999

1000

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">

<html>

<head>

<title>Errata (1st Printing)</title>

</head>

<tr>

<td>Thanks to everybody who took the time to send us an email to draw our

attention to mistakes and typos in the book. We thank our readers for reading

the book so carefully and attentively that you could spot the flaws. Thanks

a lot!

Below is a list of errors that have have been identified in the first

printing. All of these errors should be corrected in the second printing. 

Feel free to send us <a href="mailto:[email protected]">email</a> as

soon as you detect another mistake. 

</tr>

</table>

<a NAME="21"></a>page 21:

The example uses a C-style string for demonstration of the effect

of width. However, what we describe is wrong, because the maximum number

of extracted characters is <tt>width()</tt> for C++ strings and <tt>width()-1</tt>

for C string.  In our example, only 9 instead of 10 characters would 

be extracted. We should have better been using a C++ string. The example

but be corrected to:

<tt>// input</tt>

<tt>int i; <blink>string s;</blink></tt>

<tt>cin.width(10);</tt>

error found by:

Scott Barrett, Principal Member

Technical Staff

PAR Government Systems Corporation,

Rome, NY, May 2001

<a NAME="22"></a>page 22:

The code sample for demonstrating the effect of the field width

setting is misleading because the leading white spaces are not visible. 

It should be changed to:

// output

int i; char s[11];

cout.width(10);

cout <<i

<< s;

If the variables i and

s

have the following values:

i: 123

and

s: "abc"

then the output is

<blink>.......</blink>123abc

that is, seven <blink>dots</blink>

followed by the three digits representing the value of i,

followed by the character sequence contained in s.

error found by:

Bernd Mohr / Research Centre

Juelich, ZAM, Germany, August 2000

<a NAME="33"></a>page 33:

The first two paragraphs in the section on "The Stream State's Effect

on Insertion and Extraction" on page 33 is misleading and should read:

The stream state affects the behavior of the IOStreams

operations. By convention, all IOStreams operations have no effect once

the stream state indicates an error situation. More specifically, I/O operations

do nothing if the initial stream state at the time of  their invocation

includes either failbit, badbit,

or eofbit, and input and output

operations stop as soon as one of the stream state flags is set.

Note the interesting effect of the eofbit:

Extractions do not only stop in case of an error (failbit

or badbit), but also when the end

of the input stream is reached (eofbit).

Insertions typically stop only in case of an error, because no output operation

ever sets the eofbit. If, however,

the eofbit has been set before

the output operation is invoked, then the attempted insertion will fail

and have no effect. This can happen in bidirectional streams when an extraction

that reached the end of the input is followed by an insertion to the stream,

which then has the eofbit set due

to the preceeding extraction. For this reason the eofbit

in addition to the error flags failbit

and badbit stops operations on

input and bidirectional streams, but is irrelevant for operations on output

streams. 

error found by:

Bernd Mohr / Research Centre

Juelich, ZAM, Germany, August 2000

<a NAME="35"></a>page 35:

In the middle of page 35 we describe the effect of the cast operator

that converts a stream to type <tt>void*</tt> saying the following:

The cast operator <tt>operator void*()</tt> returns a zero pointer value

if <tt>failbit</tt> or <tt>badbit</tt> are set, and zero otherwise.

Of course, this is nonsense.  It must be corrected to:

The cast operator <tt>operator void*()</tt> returns a zero pointer value

if <tt>failbit</tt> or <tt>badbit</tt> are

set, and <blink>nonzero</blink>

otherwise.

error found by:

Robert P. Goddard, Senior Physicist,

University of Washington, Seattle, WA, January 2001

<a NAME="37"></a>page 37:

An alternative to wrapping the critical operations into a try block

is to suppress exceptions, execute all critical operations, and activate

them afterwards. Here is an example: 

cout.exceptions(ios_base::goodbit);

<blink>cout

<< x;</blink>

// do lots of other

stream I/O

try {cout.exceptions(ios_base::badbit

| ios_base::failbit);}

catch(ios_base::failure&

exc)

{   if (cout.bad())

{

// unrecoverable error

...

throw;

}

else

if(cout.fail())

{

// retry

...

return;

}

}

The call to <blink>cout</blink>.exceptions(ios_base::goodbit)

clears the exception mask and deactivates all exceptions. All of the subsequent

statements are executed because no exception can be thrown. Eventually,

the call to <blink>cout</blink>.exceptions

(ios_base::badbit | ios_base::failbit) is wrapped into a

try block and raises an ios_base::failure

exception

in case that any of the previously executed operations failed. 

error found by:

students of an IOStreams seminar

held at SAP AG in St. Leon-Rot, Germany, April 2000

<a NAME="38"></a>page 38:

To reset the stream state to good after an error has occured either

clear()

clear(goodbit) can

be used . Let us add a call to clear()

to the example above where we suggest to retry I/O processing. The code

changes to: 

cout.exceptions(ios_base::goodbit);

<blink>cout

<< x;</blink>

// do lots of

other stream I/O

try {cout.exceptions(ios_base::badbit

| ios_base::failbit);}

catch(ios_base::failure&

exc)

{

if (cout.bad())

{

// unrecoverable error

...

throw;

}

else if(cout.fail())

{

cout.clear();

// redo <blink>the</blink> stream I/O

that does not cause failure

return;

}

}

error in code found by:

students of an IOStreams seminar

held at SAP AG in St. Leon-Rot, Germany, April 2000

typo in comment found by:

Robert W. Hand, February 2001

<a NAME="39"></a>page 39:

The comment in the code snippet on page 39 should read:

else if(cout.fail())

{

cout.clear();

// <blink>redo those stream I/O operations that

do not cause failure</blink>

return;

}

}

error found by:

Vikram bir Singh, September

2000

<a NAME="40"></a>page 40:

The first code example on page 40 should read:

ifstream source<blink>("src.cpp")</blink>;

error found by:

Jonathan Levinson, July 2000

<a NAME="42"></a>page 42:

The last paragraph on page 42 is slightly misleading and should

read:

THE INITIAL FILE LENGTH.

The

open mode trunc (meaning

truncate)

sets the initial file length to zero, which has the effect of discarding

the file content. The trunc flag

is  included in the default open mode of output file streams, so you

can omit the trunc flag and think

of the open mode out as being equivalent

to out|trunc. This only holds true

for output file streams. For bidirectional file streams, the trunc

flag must always be explicitly specified, i.e., you must say in|out|trunc,

if the file content is to be discarded.

error found by:

Bernd Mohr / Research Centre

Juelich, ZAM, Germany, August 2000

<a NAME="43"></a>page 43:

The last code example on page 43 should read:

fstream BiStr(<blink>"poem.txt"</blink>,<blink>ios_base::in|ios_base::out</blink>);

error found by:

Clinton James, IT Director,

UCS Call One, Chicago, IL USA, July 2000 and

Vikram bir Singh, September

2000

<a NAME="45"></a>page 45:

The first code example on page 45 should read:

// bidirectional file stream opened

<blink>only

for input</blink>

fstream BiFil("poem.txt", <blink>ios_base::in</blink>);

error found by:

Vikram bir Singh, September

2000

<a NAME="48"></a>page 48:

Typically, you use in-memory I/O if the information to be read is already

available in the form of a string, or if the formatted result will be processed

as a string.  For example, to interpret the contents of a string as

an integer value, the code might look like this: 

int i;

if (istringstream("4711")

>> i)

{

//

i has the value: 4711

}

The equivalent operation in C would be a call to the <blink>sscanf()</blink>

function. However, string streams are more powerful than sscanf(),

because they use the full set of formatting facilities of IOStreams, including

internationalization for instance.

error found by:

students of an IOStreams seminar

held at SAP AG in St. Leon-Rot, Germany, April 2000

<a NAME="50"></a>page 50:

A -- is printed as a plain - in the code snippet on page 50. The

code snippet should read:

<tt> // character buffer; can store lines of length

99</tt>

<tt> // note: input adds a terminating null character </tt>

<tt> const int line_buffer_size = 100;</tt>

<tt> char buffer[line_buffer_size];</tt>

<tt> int line_number = 0;</tt>

<tt> while (cin.getline(buffer, line_buffer_size,

'\n')    // stream still good() ?</tt>

<tt>     || cin.gcount())

// any characters read ?</tt>

<tt>   int count = cin.gcount();</tt>

<tt>       // end of file

found; last line extracted</tt>

<tt>       cout <<

"Partial final line"; </tt>

<tt>   {   // max number of chars

was reached; line was longer 99 chars</tt>

<tt>       cout <<

"Partial long line";</tt>

<tt>       // clear stream

state so that we can continue reading</tt>

<tt>       cin.clear(cin.rdstate()

& ~ios::failbit);</tt>

<tt>       // don't include

newline in count</tt>

<tt>       // mind: delimiter

was extracted and counted, but not stored </tt>

<tt>       <blink>count--;</blink></tt>

<tt>       cout <<

"Line " << ++line_number;</tt>

<tt>   cout << " (" << count <<

" chars): " << buffer << endl;</tt>

error found by:

Igor V. Rafienko, Norway, September

2000

<a NAME="53"></a>page 53:

The last paragraph should read:

The error handling is omitted from the example. The functions <tt>tellp()/tellg()</tt>

indicate failure by returning the invalid stream position <tt>pos_type(-1)</tt>

and <tt>seekp()/<blink>seekg()</blink></tt>

indicate failure by setting the stream state.

error found by:

Wolfgang Kaisers, Germany,

July 2000

<a NAME="55"></a>page 55:

A -- is printed as a plain - in the code snippets on page 55. The

code snippets should read:

<tt> ofstream ostr("/tmp/fil"); </tt>

<tt> while (<blink>i--</blink>)</tt>

<tt> ofstream ostr("/tmp/fil"); </tt>

<tt> while (<blink>i--</blink>)</tt>

<tt>   ostr.flush();</tt>

error found by:

Igor V. Rafienko, Norway, September

2000

<a NAME="58"></a>page 58:

We failed to mention that sync_with_stdio is a member function of

ios_base; instead our code snippet suggests that is its a global function.

The corresponding section should read:

This synchronization is time consuming and for this reason might not

be desired in all situations. You can switch it off by calling

<tt>  <blink>ios_base::</blink>sync_with_stdio(false);</tt>

<blink>where <tt>sync_with_stdio()</tt> is

a static stream member function defined in base class <tt>ios_base</tt>. </blink>

After such a call the predefined streams will operate independently

of the C standard files, with possible performance improvements in your

C++ stream operations. 

error found by:

Igor V. Rafienko, Norway, September

2000

further improvements suggestes

by:

Robert P. Goddard, Senior Physicist,

University of Washington, Seattle, WA, January 2001

<a NAME="70"></a>page 70 and 77:

In diagrams

change basic_streamout

to <blink>basic_streambuf</blink>.

error found by:

students of an IOStreams seminar

held at SAP AG in St. Leon-Rot, Germany, April 2000

<a NAME="73"></a>page73:

On that page we describe the difference between  the base class

version of <tt>rdbuf() </tt>and the hiding version in the concrete stream

classes. The text says:

Mind the difference described in the preceding chapter between the base

class version of <tt>rdbuf() </tt>and the hiding version in the concrete

stream classes. The base class version returns the stream buffer object

referred to by the stream buffer pointer; the derived class version returns

a pointer to the embedded stream buffer object. After resetting of the

stream buffer pointer, both are different.

Astute reader Robert Goddard comments: The phrase "both

are different" is ambiguous: different from one another (true), or both

are different from their previous values (false)? I suggest the phrase

"the result of a call to the base class's rdbuf() has changed but the result

of a call to the concrete class's rdbuf() has not." Or, since you have

spelled it out elsewhere, you may choose to shorten it to "the results

of calling the two rdbuf() functions differ from one another."

Suggested reading of the section therefore is:

Mind the difference described in the preceding chapter between the base

class version of <tt>rdbuf() </tt>and the hiding version in the concrete

stream classes. The base class version returns the stream buffer object

referred to by the stream buffer pointer; the derived class version returns

a pointer to the embedded stream buffer object. After resetting of the

stream buffer pointer, <blink>the results of calling

the two <tt>rdbuf()</tt> functions differ from one another.</blink>

error found by:

Robert P. Goddard, Senior Physicist,

University of Washington, Seattle, WA, January 2001

<a NAME="85"></a>page 85:

Suggested improvement:

Class <tt>basic_streambuf<class charT, class Traits></tt> is an ”abstract”

base class in the sense that no instances of this class can be constructed.

Its constructor is protected and <blink>hence

</blink>accessible

only to derived classes. 

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="89"></a>page 89 & 90:

Typos in various places: replace "exits" by "exists":

page 89:

If the put area <blink>exists</blink>

and it is not already full, i.e. next_pointer != 0 and next_pointer <

end_pointer, then the character is put to the position the next_pointer

is referring to, and the next_pointer is incremented. 

page 90:

If the get area <blink>exists</blink>

and characters have already been read, i.e. next_pointer != 0 and begin_pointer

< next_pointer, then a putback position is available.

error found by:

Robert P. Goddard, Senior Physicist,

University of Washington, Seattle, WA, January 2001

<a NAME="92"></a>page 92:

The buffer in the diagram is

larger than intended. Correct the diagram to:

error found by:

Vikram bir Singh, October 2000

<a NAME="115"></a>page 115:

The code sample must be corrected to:

template <class charT,

class Traits>

void foo(basic_streambuf<charT,Traits>*

sbuf)

{

Traits::char_type

c;

Traits::int_type

i;

i = sbuf->sgetc();

// get the next value

// see whether it’s end-of-file

if (!<blink>Traits::</blink>eq_int_type(i,Traits::eof()))

// if not, convert it to a character

{ c = <blink>Traits::</blink>to_char_type(i);

...

// pass on the character

}

}

error found by:

Wolfgang Kaisers, Germany,

July 2000

<a NAME="144"></a>page 144:

Must read:

Invocation of <tt>erase_event</tt> callback functions on calls to <tt>copyfmt()

</tt>is

useful because <tt>copyfmt()</tt> <blink>overwrites</blink>

the original data members of the stream object.

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="152"></a>page 152-155:

The references to section 3.1.4, Refined Inserters and Extractors,

is incorrect in various places. The following pages must be corrected:

page 152:

The example in section <blink>3.1.4</blink>,

Refined Inserters and Extractors, demonstrates the correct use of sentries.

page 154:

A concrete example is shown in section <blink>3.1.4</blink>,

Refined Inserters and Extractors.

page 155:

Some of these aspects are demonstrated in the example presented in

section <blink>3.1.4</blink>, Refined

Inserters and Extractors. 

page 155:

The inserters and extractors presented in section <blink>3.1.5</blink>,

Generic Inserters and Extractors, are another demonstration of the principle. 

error found by:

Mark Rodgers   Cadenza

New Zealand Ltd, June 2000 and

Wolfgang Kaisers, Germany,

July 2000 and

Bernd Mohr / Research Centre

Juelich, ZAM, Germany, August 2000

<a NAME="156"></a>page 156:

Ignore the footnote on page 156. We initially had no intent to discuss

format control parameters, but decided later that the example would be

incomplete without it and added a section on format control (see section

3.1.4.3).  For this reason the footnote is obsolete and should be

removed.

error found by:

Bernd Mohr / Research Centre

Juelich, ZAM, Germany, August 2000

<a NAME="160"></a>page 160:

Part of the sample code for the inserter is incorrect because the

algorithm does not return the advanced output itertor as we had assumed,

but returns void instead. The corresponding code must be corrected to:

if (charToPad <= 0)

{

sink =

copy(s.begin(), s.end(), sink);

}

else

{

if (os.flags()

& ios_base::left)

{

sink = copy(s.begin(), s.end(), sink);

<blink>fill_n(sink,charToPad,os.fill());</blink>

}

else

{

<blink>fill_n(sink,charToPad,os.fill());</blink>

sink = copy(s.begin(), s.end(), sink);

}

}

error found by:

Wolfgang Kaisers, Germany,

July 2000

<a NAME="161"></a>page 161:

The  section below might be slightly misleading. We did not

mean to suggest that the C++ standard requires  dates before January

1, 1970 to be unrepresentable.

<tt>mktime()</tt> also flags date values that cannot be represented

in a <tt>tm</tt> structure, such as dates before January 1, 1970.

The C standard states that a conforming implementation of the C library

is required to document its choice of range and precision of times representable

in time_t. In all implementations that we know of the valid range starts

with January 1, 1970. In other words, whether or not a date before January

1, 1970 can be represented is implementation-defined.

Suggested improvement: add a footnote.

<tt>mktime()</tt> also flags date values that cannot be represented.<blink>*</blink>

<blink>* The range

of times representable in <tt>time_t</tt> is implementation-defined. In

many implementations of the C library dates before January 1, 1970 cannot

be represented. </blink>

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="162"></a>page 162:

The sample code is a simplification of the truth: The leap-year

rule in <tt>date::valid()</tt> is a little off. For example, 1900 wasn't

a leap year and 2100 won't be. We were deliberately trying to keep the

algorithm simple, because the focus of this section is on error indication

in inserters and extractors rather than leap-year algorithms.

Suggested improvement: add a footnote.

bool valid()

// check for sensible date; rejects nonsense like 32.12.1999<blink>*</blink>

{

...

}

<blink>*</blink> <blink>The

leap-year rule in <tt>date::valid()</tt> is simplified For example, 1900

wasn't a leap year and 2100 won't be.</blink>

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="171"></a>page 171:

The sample code for the inserter is incorrect and must be corrected

to:

template <class charT,

class Traits, <blink>class Argument</blink>>

basic_ostream<charT,

Traits>& g_inserter

(basic_ostream<charT,

Traits>& os, const Argument& <blink>arg</blink>)

{ ... }

error found by:

Ben Dorman, Ph.D.

Principal Programmer Analyst, Raytheon ITSS

Laboratory for High Energy

Astrophysics, NASA/GSFC, Greenbelt MD, April 2000

<a NAME="177"></a>page 177:

Three of the function pointer types on page 177 are incorrect and

must be corrected to:

(2) basic_ios<charT,Traits>&

(*pf)(basic_ios<charT,Traits><blink>&</blink>)

(3) basic_istream<charT,Traits>&

(*pf)(basic_istream<charT,Traits><blink>&</blink>)

(4) basic_ostream<charT,Traits>&

(*pf)(basic_ostream<charT,Traits><blink>&</blink>)

error found by:

Wayne Vucenic, Contract Programmer

No Bugs Software, Cupertino,

California, June 2001

<a NAME="180"></a>page 180:

The code samples contains some bugs. It must be corrected to:

<tt>class mendl {</tt>

<tt> public:</tt>

<tt>    explicit mendl(unsigned int i) : i_(i) {}</tt>

<tt> private:</tt>

<tt>    unsigned int i_;</tt>

<tt>    template <class charT, class Traits></tt>

<tt>    friend basic_ostream<charT,Traits>& operator<< </tt>

<tt>    (basic_ostream<charT,Traits>& os, const

mendl& w)</tt>

<tt>      // the manipulation: insert end-of-line

characters and flush</tt>

<tt>      for (int i=0; i<<blink>w.</blink>i_;

i++)</tt>

<tt>         os.put(os.widen('\n')); </tt>

<tt>      <blink>return</blink>

os.flush();</tt>

error found by:

Pete McEvoy, August 2000

<a NAME="188"></a>page 188:

The sample first code on this page has a couple of <tt>class</tt>

keyword that shouldn't be there. It should read:

template <class

charT, class Traits, class Argument>

<blink>basic_ostream<charT,Traits></blink>&

operator<<

(<blink>basic_ostream<charT,Traits></blink>&

os,

const one_arg_manip_weh<Argument>&

oamw)

{

if(os.good())

do_manip(os,oamw);

return os;

}

error found by:

Brian Chamberlain, July 2000

<a NAME="221"></a>page 221:

Freudian slip. The section must read:

The format string <tt>"%Y"</tt> produces the year <blink>with</blink>

century as a decimal number, yet the output on  the terminal is 

Hello World, this

is ths year 1/1/00

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="222"></a>page 222:

The section must read:

Consequently, setting the format string to <tt><blink>"%Y"</blink></tt>

has no effect.

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="225"></a>page 225 - 248:

Throughout chapter 3.4 all member functions that return an <tt>int_type

</tt>are

incorrectly declared: the nested type <tt>int_type </tt> must be fully

qualified with the respective class scope when the member functions are

defined outside of the class scope. The following corrections must be made:

page 231:

template <class charT,

class traits >

<blink>unbuffered_streambuf<charT,traits>::</blink>int_type

unbuffered_streambuf<charT,traits>::overflow(int_type

c)

{  ...  }

page 232:

template <class charT,

class traits >

<blink>unbuffered_streambuf<charT,traits>::</blink>int_type

unbuffered_streambuf<charT,traits>::underflow()

{  ...  }

page 232:

template <class charT,

class traits>

<blink>unbuffered_streambuf<charT,traits>::</blink>int_type

unbuffered_streambuf<charT,traits>::uflow()

{  ...  }

template <class charT,

class traits >

<blink>unbuffered_streambuf<charT,traits>::</blink>int_type

unbuffered_streambuf<charT,traits>::pbackfail(int_type

c)

{  ...  }

page 237:

template <class charT,

class traits>

<blink>outbuf<charT,traits>::</blink>int_type

outbuf<charT,traits>::overflow

(int_type c)

{  ...  }

page 240:

template <class charT,

class traits>

<blink>inbuf<charT,traits>::</blink>int_type

inbuf<charT,traits>::underflow()

{  ...  }

page 242:

template <class charT,

class traits>

<blink>inbuf<charT,traits>::</blink>int_type

inbuf<charT,traits>::pbackfail(int_type

c)

{  ...  }

error found by:

Mogens Hansen  Software

Engineer at MAN B&W Diesel A/S in Copenhagen, Denmark  and

Allan Stokes   Victoria

BC, Canada, June 2000

<a NAME="233"></a>page 233:

The signature of uflow() is incorrect and must be corrected to:

template <class charT,

class traits>

unbuffered_streambuf<charT,

traits>::int_type

<blink>unbuffered_streambuf<charT,

traits>::</blink>uflow()

{  ...  }

error found by:

Mogens Hansen  Software

Engineer

MAN B&W Diesel A/S in Copenhagen,

Denmark, June 2000

<a NAME="240"></a>page 240:

In the code snippet in the middle of the page (implementation of

the constructor) we use an interger literal, although we've already defined

a symbolic name for the constant value. This is so ugly and should be corrected

to:

template <class charT,

class traits>

inbuf<charT,traits>::inbuf()

{

setg(buffer+<blink>pbSize</blink>,

buffer+<blink>pbSize</blink>, buffer+<blink>pbSize</blink>);

}

error found by:

Allan Stokes   Victoria

BC, Canada, June 2000

<a NAME="241"></a>page 241:

Our implementation of inbuf::buffer_in() is copying overlapping

areas, which is undefined.  We should be using memmove() instead.

The code must be corrected to:

template <class charT,

class traits>

int inbuf<charT,traits>::buffer_in()

{

// determine

number of putback characters

streamsize numPutbacks

= min(gptr() - eback(), pbSize);

<blink>memmove</blink>(buffer

+ (pbSize-numPutbacks) * sizeof(char_type),

gptr() - numPutbacks * sizeof(char_type),

numPutbacks * sizeof(char_type));

int retval = buffer_from_device(buffer

+ pbSize * sizeof(char_type),

bufSize - pbSize);

if (retval <=

0)

{

setg(0,0,0);

return

-1;

}

else

{

setg(buffer

+ pbSize - numPutbacks,

buffer

+ pbSize, buffer + pbSize + retval);

return

retval;

}

}

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="242"></a>page 242:

Typo. Section must read:

Again, the error handling in <tt><blink>underflow()</blink></tt>is

oversimplified in that it always returns <tt>traits_type::eof()</tt> to

indicate failure, regardless of the source of the error.

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="245"></a>page 245:

The description of showmanyc() could be more precise.  Suggested

improvement:

The virtual member function <tt>showmanyc()</tt> (pronounced “ess-how-many-see,”

not “show-manic”) returns an estimation of the number of characters available

for input, or <tt>-1</tt>. <blink>If the returned

value is positive, then at least the indicated number of characters can

be made available by one or more calls to <tt>underflow()</tt>. </blink>If

the operations returns <tt>-1</tt>, calls to <tt>underflow() </tt>and <tt>uflow()

</tt>will

fail. The intent is not only to know in advance that these calls will not

return <tt>traits_type::eof()</tt>, but that they will return “immediately.”

Or, to put it more simply, the purpose of this operation is to check if

characters are available on the external device, which can be read by <tt>underflow()

</tt>or

<tt>uflow()

</tt>without

waiting.

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="255"></a>page 255:

The example of a Greek date format is slightly incorrect: The iota

used in the name of the day and the name of the month must be accented

using the Unicode character  03AF. <a href="greekDateFormat.html">Click

here</a> for the correct format using ISO-8859-7 character encoding.

error found by:

Klitos Kyriacou UK, March 2001

<a NAME="272"></a>page 272:

Typo in page. Should read:

The reference returned remains valid at least as long as any copy of

the containing locale exists. Section <blink>7.3</blink>,

Memory Management of Facets in a Locale, explains why this is and how it

works.

Typo in footnote. Should read:

4. The facet type <tt>money_put<char, string_inserter<char> >

</tt>is

an instantiation of the <tt>money_put</tt> template for an output iterator

other than the default, which is <tt>ostreambuf_iterator<charT>

</tt>and

was omitted from the list of template arguments in <tt><blink>money_put<char></blink></tt>.

...

error found by:

Klaus Wittlich, Cologne Germany,

December 2000

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

Steve Love, UK, April 2001

<a NAME="275"></a>page 275:

Typo in page. Should read:

To be more precise, we should say that in every locale there is one

representative of each standard facet family. Remember, we mentioned before,

at the beginning of chapter <blink>5</blink>,

that facet types are organized in facet families, that is, hierarchies

of facet classes derived from each other.

error found by:

James M. Stern,

ITG, Inc., Culver City, CA, April 2001

<a NAME="281"></a>page 281:

Typo in the code sample. Must read:

<tt>template <class String></tt>

<tt>String* compare1toM (<blink>locale</blink>

loc, String one, String* begin, String* end)</tt>

<tt>  const collate<String::value_type>& collateFacet =</tt>

<tt>

use_facet< collate<String::value_type> >(loc);</tt>

<tt>  String tmpOne = </tt>

<tt>          collateFacet.transform(one.c_str(),one.c_str()+one.length());</tt>

<tt>  for (; begin < end ; begin++)</tt>

<tt>    String tmpMany = collateFacet.transform((*begin).c_str(),</tt>

<tt>

(*begin).c_str()+(*begin).length());</tt>

<tt>    if (tmpOne == tmpMany)</tt>

<tt>      return(begin);</tt>

<tt>  return (end);</tt>

error found by:

Norihisa Kitazawa, Japan, April

2001

<a NAME="284"></a>page 284:

View remainder of file in raw view

FilesExpand file tree

data-small.txt

Latest commit

History

data-small.txt

File metadata and controls