Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On High Performance Programming with Qt 5

You're reading from   Hands-On High Performance Programming with Qt 5 Build cross-platform applications using concurrency, parallel programming, and memory management

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781789531244
Length 384 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Marek Krajewski Marek Krajewski
Author Profile Icon Marek Krajewski
Marek Krajewski
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Understanding Performant Programs FREE CHAPTER 2. Profiling to Find Bottlenecks 3. Deep Dive into C++ and Performance 4. Using Data Structures and Algorithms Efficiently 5. An In-Depth Guide to Concurrency and Multithreading 6. Performance Failures and How to Overcome Them 7. Understanding I/O Performance and Overcoming Related Problems 8. Optimizing Graphical Performance 9. Optimizing Network Performance 10. Qt Performance on Embedded and Mobile Platforms 11. Testing and Deploying Qt Applications 12. Assessments 13. Other Books You May Enjoy

Chapter 7

  1. Why will reading from std::cin first flush std::cout?
    Because they are tied by default—std::cin.tie(&std::cout);
  2. What is the difference between a unit-buffered, a line-buffered, a fully-buffered, and an unbuffered stream?
    A unit-buffered stream will flush after each >>, a line-buffered stream after each \n, a fully-buffered stream when the internal buffers are full, and unbuffered ones after each write.
  3. Why is std::iostream slower than std::filebuf and fprintf() slower that puts()?
    Because iostream will perform newline translation and locale-based conversions that filebuf doesn't have to. fprintf() must scan the format string in runtime; puts() doesn't have a format string.
    By the way, it is possible to scan a format string in compile time in C++ using template metaprogramming tricks!
  4. Why does Linux kill processes simply if it feels like it...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image