mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-02-07 04:10:08 +00:00
Fixed a linux time issue. Removed a blank line from the jucer's .sln file generator. Cleaned up some jucer code.
This commit is contained in:
parent
952b8c3940
commit
4e52fac18e
24 changed files with 165 additions and 261 deletions
|
|
@ -167,8 +167,23 @@ private:
|
|||
const ScopedPointer* getAddress() const throw() { return this; }
|
||||
|
||||
#if ! JUCE_MSVC // (MSVC can't deal with multiple copy constructors)
|
||||
// This is private to stop people accidentally copying a const ScopedPointer (the compiler
|
||||
// will let you do so by implicitly casting the source to its raw object pointer).
|
||||
/* This is private to stop people accidentally copying a const ScopedPointer (the compiler
|
||||
would let you do so by implicitly casting the source to its raw object pointer).
|
||||
|
||||
A side effect of this is that you may hit a puzzling compiler error when you write something
|
||||
like this:
|
||||
|
||||
ScopedPointer<MyClass> m = new MyClass(); // Compile error: copy constructor is private.
|
||||
|
||||
Even though the compiler would normally ignore the assignment here, it can't do so when the
|
||||
copy constructor is private. It's very easy to fis though - just write it like this:
|
||||
|
||||
ScopedPointer<MyClass> m (new MyClass()); // Compiles OK
|
||||
|
||||
It's good practice to always use the latter form when writing your object declarations anyway,
|
||||
rather than writing them as assignments and assuming (or hoping) that the compiler will be
|
||||
smart enough to replace your construction + assignment with a single constructor.
|
||||
*/
|
||||
ScopedPointer (const ScopedPointer&);
|
||||
#endif
|
||||
};
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue