Home
last modified time | relevance | path

Searched refs:clarify (Results 1 – 25 of 73) sorted by relevance

123

/openbsd/src/gnu/usr.bin/cvs/windows-NT/SCC/
DChangeLog32 * README.txt: Update and clarify various minor points.
/openbsd/src/usr.bin/indent/
DREADME70 In any case, there appears to be noone at UofI to clarify/and change
/openbsd/src/gnu/llvm/clang/lib/Analysis/
DCalledOnceCheck.cpp511 static std::optional<Clarification> clarify(const CFGBlock *Conditional, in clarify() function in __anon2384fff10111::NotCalledClarifier
949 if (auto Clarification = NotCalledClarifier::clarify(Parent, Succ)) { in findAndReportNotCalledBranches()
/openbsd/src/gnu/usr.bin/perl/pod/
Dperl5122delta.pod143 L<perlrun> has been updated to clarify the behaviour of octal flags to F<perl>.
Dperl5222delta.pod113 The documentation of L<C<hex()>|perlfunc/hex> has been revised to clarify valid
Dperlsecpolicy.pod360 The security team may ask you to clarify the exact name we should use
Dperl5240delta.pod831 and clarify the documentation for some of the existing entries, and
856 The documentation of C<hex> has been revised to clarify valid inputs.
997 The documentation of C<$@> was reworded to clarify that it is not just for
Dperlintro.pod156 occasionally to clarify issues of precedence.
Dperlpodspec.pod203 This section is intended to supplement and clarify the discussion in
1135 will hopefully clarify what it means and how processors should deal
Dperl5300delta.pod752 Try to clarify that C<< ref(qr/xx/) >> returns C<Regexp> rather than
Dperldocstyle.pod283 You may include comments within example code to further clarify or label
Dperl589delta.pod1254 L<perlrun> is updated to clarify on the hash seed I<PERL_HASH_SEED>. Also more
/openbsd/src/usr.bin/vi/cl/
DREADME.signal62 on DISCARD and LNEXT. To clarify, what vi WANTS is 8-bit clean, with
/openbsd/src/gnu/llvm/clang/docs/analyzer/developer-docs/
DDebugChecks.rst108 argument is technically unnecessary but is intended to clarify intent.
/openbsd/src/gnu/llvm/clang/docs/
DClangTransformerTutorial.rst211 to the source headers for up-to-date information. First, though, we clarify what
/openbsd/src/gnu/usr.bin/cvs/doc/
DChangeLog1942 * cvsclient.texi (Requests): For Notify request, clarify a few
2023 response. Also clarify that clients will tend to store the
2026 * cvsclient.texi (Requests): Further clarify Directory example.
3031 on complex and unknown security bugs to clarify that it is
3389 * cvs.texinfo (Moving files): Rewrite "Outside" node to clarify
Dcvs.info-4392 To help clarify the file status, `status' also reports the `Working
/openbsd/src/gnu/usr.bin/cvs/os2/
DChangeLog180 * README: Try to clarify status vis-a-vis client vs. local.
/openbsd/src/gnu/usr.bin/gcc/gcc/f/
DChangeLog2261 * g77.texi: Rename options in docs, clarify usage.
2262 * lang-options.h: Rename options, clarify doclets.
2962 * g77.texi: Properly attribute Priest document; clarify
/openbsd/src/gnu/usr.bin/binutils/gdb/doc/
DChangeLog2356 * gdb.texinfo: Wrap "ASCII" in @sc{}; clarify a few sentences.
2411 * gdb.texinfo: Include details specific to DOS host, clarify
3658 * stabs.texinfo (Builtin Type Descriptors): Try to clarify what
/openbsd/src/usr.bin/lex/
DChangeLog1042 * NEWS: clarify NEWS item re man page and pdf manual
1203 clarify example
4859 * TODO: clarify item on comments in lexical files
4990 * TODO: flex.texi is here; clarify tests/ rewrite issue
5245 * autogen.sh: clarify usage instructions; prepare tests/ as well
5643 * Makefile.in: clarify when 8-bit scanners are created by default,
/openbsd/src/gnu/usr.bin/binutils/binutils/
DChangeLog-98991805 * binutils.texi: Update and clarify.
/openbsd/src/gnu/usr.bin/binutils-2.17/binutils/
DChangeLog-98991805 * binutils.texi: Update and clarify.
/openbsd/src/gnu/usr.bin/cvs/src/
DChangeLog-971433 * subr.c (xmalloc): Reword error message to clarify that memory,
1508 * server.c (server_modtime): Add assertion to clarify that caller
/openbsd/src/gnu/llvm/llvm/docs/
DSourceLevelDebugging.rst1548 values, we can clarify the contents of the ``BUCKETS``, ``HASHES`` and

123