/macosx-10.10.1/emacs-93/emacs/lisp/mh-e/ |
H A D | mh-thread.el | 194 (setq done 'failure))))) 196 ((eq done 'failure) (goto-char point))
|
/macosx-10.10.1/llvmCore-3425.0.34/lib/Support/Unix/ |
H A D | Program.inc | 361 // itself apparently does not), check to see if the failure was due to some
|
/macosx-10.10.1/ruby-106/ruby/test/minitest/ |
H A D | test_minitest_unit.rb | 99 rescue MiniTest::Assertion => failure 100 failure
|
/macosx-10.10.1/vim-55/runtime/syntax/ |
H A D | vhdl.vim | 48 syn keyword vhdlStatement note warning error failure
|
H A D | d.vim | 37 " - Maybe highlight the 'exit', 'failure', and 'success' parts of the
|
H A D | rexx.vim | 99 syn match rexxRaise "\(^\|;\|:\)\s\+\<raise\>\s*\<\(propagate\|error\|failure\|syntax\|user\)\>\?" contains=rexxRaise2
|
/macosx-10.10.1/Security-57031.1.35/SecurityTests/regressions/inc/Test/ |
H A D | More.pm | 111 failure. 289 So why use these? They produce better diagnostics on failure. ok() 366 diagnostics on failure. 1076 treat it as a normal failure. See L<CAVEATS and NOTES>). 1438 considered a failure and will exit with 255.
|
H A D | Builder.pm | 1190 a failing test (C<ok() || diag()>) it "passes through" the failure. 1824 considered a failure and will exit with 255.
|
/macosx-10.10.1/bind9-45.101/bind9/lib/dns/ |
H A D | masterdump.c | 1715 goto failure; 1718 goto failure; 1723 failure:
|
/macosx-10.10.1/Security-57031.1.35/Security/regressions/inc/IPC/ |
H A D | Run3.pm | 88 =item + returns TRUE on success, FALSE on failure 444 ## This routine procedes in stages so that a failure in an early
|
/macosx-10.10.1/Security-57031.1.35/SecurityTests/regressions/t/IPC/ |
H A D | Run3.pm | 88 =item + returns TRUE on success, FALSE on failure 444 ## This routine procedes in stages so that a failure in an early
|
/macosx-10.10.1/security_systemkeychain-55202/src/ |
H A D | cs_utils.cpp | 487 } catch (const Fail &failure) {
|
/macosx-10.10.1/Security-57031.1.35/SecurityTests/regressions/inc/ |
H A D | Test.pm | 58 ok(0); # failure 61 ok(0); # ok, expected failure (see todo list, above) 64 ok(0,1); # failure: '0' ne '1' 65 ok('broke','fixed'); # failure: 'broke' ne 'fixed' 70 ok(sub { 1+1 }, 3); # failure: '2' ne '3' 774 of hash refs that describe each test failure. Each hash will contain 783 particularly bizarre test failure. However it's not a panacea. Core
|
/macosx-10.10.1/bind9-45.101/bind9/bin/dig/ |
H A D | dighost.c | 571 fatal("memory allocation failure in %s:%d", 664 fatal("memory allocation failure"); 731 fatal("memory allocation failure in %s:%d", 926 fatal("memory allocation failure in %s:%d", 931 goto failure; 937 goto failure; 942 goto failure; 947 failure: 1120 goto failure; 1145 goto failure; [all...] |
/macosx-10.10.1/llvmCore-3425.0.34/lib/Support/Windows/ |
H A D | PathV2.inc | 137 // A zero return value indicates a failure other than insufficient space.
|
/macosx-10.10.1/apache-793/httpd/modules/dav/main/ |
H A D | mod_dav.c | 1210 ** Note that a failure on the resource itself does not generate a 1978 /* ### what to do about closing the propdb on server failure? */ 2282 int failure = 0; local 2341 /* ### what to do about closing the propdb on server failure? */ 2388 failure = 1; 2396 if (!failure && dav_process_ctx_list(dav_prop_exec, ctx_list, 1, 0)) { 2397 failure = 1; 2400 /* generate a failure/success response */ 2401 if (failure) { 2414 dav_auto_checkin(r, resource, failure, [all...] |
/macosx-10.10.1/mDNSResponder-561.1.1/mDNSShared/ |
H A D | dnsextd.c | 407 // Return a DNS Message read off of a TCP socket, or NULL on failure 762 if (!request || !reply) { vlogmsg = "NULL message"; goto failure; } 763 if (request->len < sizeof(DNSMessageHeader) || reply->len < sizeof(DNSMessageHeader)) { vlogmsg = "Malformatted message"; goto failure; } 767 { vlogmsg = "Request opcode not an update"; goto failure; } 770 if ((reply->msg.h.flags.b[1] & kDNSFlag1_RC_Mask)) { vlogmsg = "Reply contains non-zero rcode"; goto failure; } 772 { vlogmsg = "Reply opcode not an update response"; goto failure; } 777 failure:
|
/macosx-10.10.1/emacs-93/emacs/lisp/textmodes/ |
H A D | bibtex.el | 1341 end-point failure boundaries) 1342 (while (not (or end-point failure)) 1347 ((setq failure t))) 1352 (if (and (not failure) 2623 failure) 2635 (while (and (not failure) 2641 (setq failure t)) 2644 (setq failure t)))) 2645 (if failure 3713 name start-text end-text end failure don [all...] |
/macosx-10.10.1/BerkeleyDB-21/db/perl/BerkeleyDB/t/Test/ |
H A D | Builder.pm | 993 a failing test (C<ok() || diag()>) it "passes through" the failure. 1545 considered a failure and will exit with 255.
|
/macosx-10.10.1/CPANInternal-159.1/Config-Std-0.900/lib/Config/ |
H A D | Std.pm | 814 The subroutine returns true on success, and throws an exception on failure. 863 The subroutine returns true on success and throws and exception on failure.
|
/macosx-10.10.1/CPANInternal-159.1/Config-Std-0.901/lib/Config/ |
H A D | Std.pm | 816 The subroutine returns true on success, and throws an exception on failure. 865 The subroutine returns true on success and throws and exception on failure.
|
/macosx-10.10.1/tcl-105/tcl_ext/tclae/tclae/tests/ |
H A D | tclAEDesc.test | 130 test tclAEDesc-2.5 {tclAE::coerceDesc failure} {macOnly tclAEshlb} {
|
/macosx-10.10.1/CPANInternal-159.1/Template-Toolkit-2.25/lib/Template/ |
H A D | Service.pm | 430 indicate failure. The appropriate error message can be retrieved via the
|
/macosx-10.10.1/Security-57031.1.35/SecurityTests/regressions/inc/Test/Builder/ |
H A D | Tester.pm | 208 Because the standard failure message that B<Test::Builder> produces
|
/macosx-10.10.1/emacs-93/emacs/lisp/ |
H A D | allout.el | 604 needed - show reminder on passphrase entry failure 1485 (condition-case failure 1491 failure) 4673 (condition-case failure 4675 (error failure))
|