Home
last modified time | relevance | path

Searched refs:ran (Results 1 – 25 of 56) sorted by relevance

123

/freebsd-9-stable/contrib/tcsh/
Dtw.comp.c194 tw_pos(Char *ran, int wno) in tw_pos() argument
198 if (ran[0] == '*' && ran[1] == '\0') in tw_pos()
201 for (p = ran; *p && *p != '-'; p++) in tw_pos()
205 return wno == getn(ran); in tw_pos()
207 if (ran == p) /* range = - <number> */ in tw_pos()
208 return wno <= getn(&ran[1]); in tw_pos()
212 return getn(ran) <= wno; in tw_pos()
214 return (getn(ran) <= wno) && (wno <= getn(p)); in tw_pos()
523 Char *ran, /* The pattern or range X/<range>/XXXX/ */ in tw_complete() local
561 ptr = tw_dollar(&ptr[2], wl, wordno, &ran, sep, in tw_complete()
[all …]
DFAQ48 3. I ran 'dbxtool &' and 'shelltool &' from tcsh, and they end up in
253 correctly when ran on hp/ux-11.x systems.
/freebsd-9-stable/cddl/contrib/dtracetoolkit/Examples/
Dsh_who_example.txt17 We see func_abc.sh ran three seperate times, each with nine lines of shell
42 Firefox itself (PID 13677) ran 75 lines of code. There are also instances of
Dcputimes_example.txt169 svc.startd ran for 51 microseconds, and soffice.bin ran for 28 milliseconds.
Dphp_cpudist_example.txt71 microseconds and 63 microseconds on CPU; sleep ran three times and each time
Dpriclass_example.txt77 on a Solaris system. I ran an infinite shell loop to create heavy activity,
Dpl_flow_example.txt177 After initialising Perl libraries and modules, the "nicstat" program ran,
Dpl_flowtime_example.txt182 After initialising Perl libraries and modules, the "nicstat" program ran,
Dpl_flowinfo_example.txt186 After initialising Perl libraries and modules, the "nicstat" program ran,
/freebsd-9-stable/contrib/file/magic/Magdir/
Dalliant10 # big-endian or little-endian versions, depending on the mode they ran
/freebsd-9-stable/cddl/contrib/dtracetoolkit/Notes/
DALLperl_notes.txt33 ran from the "hello_strict.pl" program - which doesn't appear to use "BEGIN",
/freebsd-9-stable/contrib/llvm/patches/
Dpatch-r296800-llvm-r219512-out-of-registers.diff14 This fixes a possible "ran out of registers" error when compiling
Dpatch-r263313-llvm-r203311-fix-sse1-oom.diff11 I ran this over the test suite with i686 and mattr=+sse and saw no regressions.
/freebsd-9-stable/etc/
Dremote48 # 14.4k and 28.8k modems ran the port at 4x. Some rare 19.2 baud modems
/freebsd-9-stable/contrib/amd/
DREADME.attrcache64 nfs_args all to 1, the smallest non-zero value we could. When we ran the
/freebsd-9-stable/contrib/nvi/docs/internals/
Dquoting68 As ex ran in canonical mode, there was little work that it
/freebsd-9-stable/contrib/gdb/
Dconfig-ml.in167 # two files: one that only the library's toplevel configure.in ran (to
168 # configure the multilib subdirs), and another that all configure.in's ran to
/freebsd-9-stable/contrib/binutils/gprof/po/
Dgprof.pot235 msgid "%s: ran out room for %lu bytes of text space\n"
Dms.po258 msgid "%s: ran out room for %lu bytes of text space\n"
/freebsd-9-stable/contrib/binutils/
Dconfig-ml.in172 # two files: one that only the library's toplevel configure.in ran (to
173 # configure the multilib subdirs), and another that all configure.in's ran to
/freebsd-9-stable/crypto/openssl/crypto/rc4/
Drrc4.doc126 and ran them through both algorithms. The algorithms appear to
/freebsd-9-stable/contrib/bind9/doc/misc/
Dmigration137 dns_rdata_fromtext: local.db:119: ran out of space
/freebsd-9-stable/contrib/cvs/
DChangeLog4338 * configure: re-ran autoconf.
4557 * configure, config.h.in: re-ran autoconf
4598 * configure: re-ran autoconf
4632 * configure: re-ran autoconf.
4724 * (configure): Re-ran autoconf.
4737 * (configure): re-ran autoconf following Peter Wemm's change
4747 * (configure): re-ran autoconf.
4976 * configure: re-ran autoconf-2.4
/freebsd-9-stable/contrib/gnu-sort/
DTHANKS164ran Uddeborg goeran@uddeborg.pp.se
/freebsd-9-stable/contrib/libpcap/
DINSTALL.txt95 if you already ran configure once).

123