@@ -61,8 +61,8 @@ namespace cv
61
61
#ifdef CV_COLLECT_IMPL_DATA
62
62
CV_EXPORTS void setImpl (int flags); // set implementation flags and reset storage arrays
63
63
CV_EXPORTS void addImpl (int flag, const char * func = 0 ); // add implementation and function name to storage arrays
64
- // Get stored implementation flags and fucntions names arrays
65
- // Each implementation entry correspond to function name entry, so you can find which implementation was executed in which fucntion
64
+ // Get stored implementation flags and functions names arrays
65
+ // Each implementation entry correspond to function name entry, so you can find which implementation was executed in which function
66
66
CV_EXPORTS int getImpl (std::vector<int > &impl, std::vector<String> &funName);
67
67
68
68
CV_EXPORTS bool useCollection (); // return implementation collection state
@@ -196,7 +196,7 @@ be called outside of parallel region.
196
196
OpenCV will try to run it's functions with specified threads number, but some behaviour differs from
197
197
framework:
198
198
- `TBB` – User-defined parallel constructions will run with the same threads number, if
199
- another does not specified. If late on user creates own scheduler, OpenCV will be use it.
199
+ another does not specified. If later on user creates own scheduler, OpenCV will use it.
200
200
- `OpenMP` – No special defined behaviour.
201
201
- `Concurrency` – If threads == 1, OpenCV will disable threading optimizations and run it's
202
202
functions sequentially.
@@ -229,7 +229,7 @@ CV_EXPORTS_W int getNumThreads();
229
229
returns 0 if called outside of parallel region.
230
230
231
231
The exact meaning of return value depends on the threading framework used by OpenCV library:
232
- - `TBB` – Unsupported with current 4.1 TBB release. May be will be supported in future.
232
+ - `TBB` – Unsupported with current 4.1 TBB release. Maybe will be supported in future.
233
233
- `OpenMP` – The thread number, within the current team, of the calling thread.
234
234
- `Concurrency` – An ID for the virtual processor that the current context is executing on (0
235
235
for master thread and unique number for others, but not necessary 1,2,3,...).
@@ -636,7 +636,7 @@ class TLSData : protected TLSDataContainer
636
636
public:
637
637
inline TLSData () {}
638
638
inline ~TLSData () { release (); } // Release key and delete associated data
639
- inline T* get () const { return (T*)getData (); } // Get data assosiated with key
639
+ inline T* get () const { return (T*)getData (); } // Get data associated with key
640
640
641
641
// Get data from all threads
642
642
inline void gather (std::vector<T*> &data) const
@@ -687,7 +687,7 @@ The sample below demonstrates how to use CommandLineParser:
687
687
688
688
### Keys syntax
689
689
690
- The keys parameter is a string containing several blocks, each one is enclosed in curley braces and
690
+ The keys parameter is a string containing several blocks, each one is enclosed in curly braces and
691
691
describes one argument. Each argument contains three parts separated by the `|` symbol:
692
692
693
693
-# argument names is a space-separated list of option synonyms (to mark argument as positional, prefix it with the `@` symbol)
@@ -845,7 +845,7 @@ class CV_EXPORTS CommandLineParser
845
845
846
846
/* * @brief Check for parsing errors
847
847
848
- Returns true if error occured while accessing the parameters (bad conversion, missing arguments,
848
+ Returns true if error occurred while accessing the parameters (bad conversion, missing arguments,
849
849
etc.). Call @ref printErrors to print error messages list.
850
850
*/
851
851
bool check () const ;
0 commit comments