1
0
Fork 0
mirror of https://github.com/juce-framework/JUCE.git synced 2026-01-08 23:24:19 +00:00

Docs: Update language to be more diplomatic

This commit is contained in:
reuk 2025-11-13 20:19:49 +00:00
parent 83e5264c86
commit e465b71188
No known key found for this signature in database
9 changed files with 34 additions and 17 deletions

View file

@ -1239,7 +1239,7 @@ private:
bool isOutput = (ioid != "Input");
bool isInput = (ioid != "Output");
// alsa is stupid here, it advertises dmix and dsnoop as input/output devices, but
// ALSA advertises dmix and dsnoop as input/output devices, but
// opening dmix as input, or dsnoop as output will trigger errors
isInput = isInput && ! id.startsWith ("dmix");
isOutput = isOutput && ! id.startsWith ("dsnoop");

View file

@ -398,8 +398,8 @@ public:
// if this fails, the host hasn't called resume() before processing
jassert (isProcessing);
// (tragically, some hosts actually need this, although it's stupid to have
// to do it here.)
// (tragically, some hosts actually need this, although it's unfortunate to have
// to do it here)
if (! isProcessing)
resume();

View file

@ -43,7 +43,6 @@
// <cstring> or <string.h>, which prevents the use of stricmp in JUCE source.
#include <cstring>
// Wow, those Steinberg guys really don't worry too much about compiler warnings.
JUCE_BEGIN_IGNORE_WARNINGS_LEVEL_MSVC (0, 4505 4702 6011 6031 6221 6386 6387 6330 6001 28199)
JUCE_BEGIN_IGNORE_WARNINGS_GCC_LIKE ("-W#warnings",

View file

@ -1000,7 +1000,7 @@ public:
the correct size before returning it. If you implement this method, you must
also implement the hasEditor() method and make it return true.
Remember not to do anything silly like allowing your processor to keep a pointer to
Remember not to do anything like allowing your processor to keep a pointer to
the component that gets created - it could be deleted later without any warning, which
would make your pointer into a dangler. Use the getActiveEditor() method instead.

View file

@ -81,9 +81,15 @@ private:
the 'OwnerClass' template parameter - the name and stack trace of its creation should
have been printed by the lines above.
If you're leaking, it's probably because you're using old-fashioned, non-RAII techniques for
your object management. Tut, tut. Always, always use std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoid the 'delete' operator at all costs!
Many errors like this are caused by using old-fashioned, non-RAII techniques for
object management. If you're seeing this, it's a good idea to double-check
that you're using std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoiding manual calls to the 'delete'
operator at all costs!
You may also see this error if JUCE's shutdown code is called while an object
containing a leak detector is still alive (perhaps declared as a namespace-scope
static).
*/
jassertfalse;
}

View file

@ -73,9 +73,15 @@ public:
not be this particular deletion that's at fault - the incorrect one may have happened
at an earlier point in the program, and simply not been detected until now.
Most errors like this are caused by using old-fashioned, non-RAII techniques for
your object management. Tut, tut. Always, always use std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoid the 'delete' operator at all costs!
Many errors like this are caused by using old-fashioned, non-RAII techniques for
object management. If you're seeing this, it's a good idea to double-check
that you're using std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoiding manual calls to the 'delete'
operator at all costs!
You may also see this error if JUCE's shutdown code is called while an object
containing a leak detector is still alive (perhaps declared as a namespace-scope
static).
*/
jassertfalse;
}
@ -97,9 +103,15 @@ private:
/** If you hit this, then you've leaked one or more objects of the type specified by
the 'OwnerClass' template parameter - the name should have been printed by the line above.
If you're leaking, it's probably because you're using old-fashioned, non-RAII techniques for
your object management. Tut, tut. Always, always use std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoid the 'delete' operator at all costs!
Many errors like this are caused by using old-fashioned, non-RAII techniques for
object management. If you're seeing this, it's a good idea to double-check
that you're using std::unique_ptrs, OwnedArrays,
ReferenceCountedObjects, etc, and avoiding manual calls to the 'delete'
operator at all costs!
You may also see this error if JUCE's shutdown code is called while an object
containing a leak detector is still alive (perhaps declared as a namespace-scope
static).
*/
jassertfalse;
}

View file

@ -276,7 +276,7 @@
#include <cpu-features.h>
#endif
// Need to clear various moronic redefinitions made by system headers.
// Need to clear various redefinitions made by system headers.
#undef max
#undef min
#undef direct

View file

@ -295,7 +295,7 @@ void JUCE_CALLTYPE Process::terminate()
_CrtDumpMemoryLeaks();
#endif
// bullet in the head in case there's a problem shutting down
// force exit in case there's a problem shutting down
ExitProcess (1);
}

View file

@ -552,7 +552,7 @@ public:
glEnable (GL_TEXTURE_2D);
#if JUCE_WINDOWS
// some stupidly old drivers are missing this function, so try to at least avoid a crash here,
// some old drivers are missing this function, so try to at least avoid a crash here,
// but if you hit this assertion you may want to have your own version check before using the
// component rendering stuff on such old drivers.
jassert (context.extensions.glActiveTexture != nullptr);