diff options
Diffstat (limited to 'doc/html/templates.html')
| -rw-r--r-- | doc/html/templates.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/templates.html b/doc/html/templates.html index cd08a1604..a7335e534 100644 --- a/doc/html/templates.html +++ b/doc/html/templates.html @@ -69,7 +69,7 @@ C++ source file generated by the <tt>moc</tt> must be compiled and linked with the implementation of the class (or it can be <tt>#included</tt> into the class's source file). Typically <tt>moc</tt> is not called manually, but automatically by the build system, so it -retquires no additional effort by the programmer. +requires no additional effort by the programmer. <p> There are other precompilers, for example, <tt>rpc</tt> and <tt>idl</tt>, that enable programs or objects to communicate over process or machine boundaries. The alternatives to precompilers are @@ -95,7 +95,7 @@ of Objective C when it comes to component-based graphical user interface programming. What's good for a high end database server or an operating system isn't necessarily the right design choice for a GUI frontend. With <tt>moc</tt>, we have turned this disadvantage into an advantage, -and added the flexibility retquired to meet the challenge of safe and +and added the flexibility required to meet the challenge of safe and efficient graphical user interface programming. <p> Our approach goes far beyond anything you can do with templates. For example, we can have object properties. And we can have overloaded @@ -116,7 +116,7 @@ generated and connected from TQt Designer's XML <tt>ui</tt> files. <p> TQt's signals and slots implementation is not as fast as a template-based solution. While emitting a signal is approximately the cost of four ordinary function calls with common template implementations, TQt -retquires effort comparable to about ten function calls. This is not +requires effort comparable to about ten function calls. This is not surprising since the TQt mechanism includes a generic marshaller, introspection and ultimately scriptability. It does not rely on excessive inlining and code expansion and it provides unmatched runtime @@ -132,7 +132,7 @@ cost of the call is only a small proportion of the entire cost of a slot. Benchmarking against TQt's signals and slots system is typically done with empty slots. As soon as you do anything useful in your slots, for example a few simple string operations, the calling overhead becomes -negligible. TQt's system is so optimized that anything that retquires +negligible. TQt's system is so optimized that anything that requires operator new or delete (for example, string operations or inserting/removing something from a template container) is significantly more expensive than emitting a signal. @@ -140,7 +140,7 @@ more expensive than emitting a signal. of a performance critical task and you identify this connection as the bottleneck, think about using the standard listener-interface pattern rather than signals and slots. In cases where this occurs, you probably -only retquire a 1:1 connection anyway. For example, if you have an object +only require a 1:1 connection anyway. For example, if you have an object that downloads data from the network, it's a perfectly sensible design to use a signal to indicate that the requested data arrived. But if you need to send out every single byte one by one to a consumer, use a |