Home
last modified time | relevance | path

Searched refs:ordering (Results 1 – 25 of 40) sorted by relevance

12

/onnv-gate/usr/src/grub/grub-0.97/lib/
H A Dgetopt.c190 } ordering; variable
412 ordering = RETURN_IN_ORDER;
417 ordering = REQUIRE_ORDER;
421 ordering = REQUIRE_ORDER;
423 ordering = PERMUTE;
556 if (ordering == PERMUTE)
609 if (ordering == REQUIRE_ORDER)
/onnv-gate/usr/src/uts/common/io/hxge/
H A Dhxge_defs.h40 #error Bit ordering not defined
/onnv-gate/usr/src/cmd/perl/5.8.4/distrib/lib/Text/TabsWrap/t/
H A Dfill.t44 You can find details out about the book as well as ordering information at
/onnv-gate/usr/src/common/openssl/doc/ssl/
H A DSSL_CTX_load_verify_locations.pod41 is performed in the ordering of the extension number, regardless of other
/onnv-gate/usr/src/tools/scripts/
H A Dits.reg34 # reference should be inferred from this ordering. Applications
/onnv-gate/usr/src/cmd/perl/5.8.4/distrib/ext/Encode/t/
H A Dencoding.t144 #string ordering
/onnv-gate/usr/src/cmd/perl/5.8.4/distrib/pod/
H A Dperl581delta.pod34 Mainly due to security reasons, the "random ordering" of hashes
40 B<Perl has never guaranteed any ordering of the hash keys>, and the
41 ordering has already changed several times during the lifetime of
42 Perl 5. Also, the ordering of hash keys has always been, and
61 subroutines) have assumed any particular ordering to the global
72 some particular ordering of hash elements, and outright bugs: it
H A Dperlsec.pod443 B<Perl has never guaranteed any ordering of the hash keys>, and the
444 ordering has already changed several times during the lifetime of
445 Perl 5. Also, the ordering of hash keys has always been, and
H A Dperlre.pod1247 For this grouping operator there is no need to describe the ordering, since
1252 The ordering is the same as for the regular expression which is
1258 already determined. The ordering of the matches is the same as for the
1263 The above recipes describe the ordering of matches I<at a given position>.
H A Dperlpacktut.pod324 the byte ordering: whether the first byte is the least or most
336 C<ON> or C<NO> (depending on your system's byte ordering) - or something
384 Requesting a particular byte ordering may be necessary when you work with
H A Dperllocale.pod469 (ordering) of characters. For example, 'b' follows 'a' in Latin
508 dictionary-like ordering that ignores space characters completely and
H A Dperldata.pod630 of how to arrange for an output ordering.
/onnv-gate/usr/src/cmd/pack/
H A Dpack.c103 #error Unknown byte ordering!
/onnv-gate/usr/src/cmd/tcpd/
H A DREADME.NIS7 > name. This behavior seems to be random, may depend on ordering in
/onnv-gate/usr/src/common/openssl/crypto/des/asm/
H A Dreadme127 but for the pentium it has been replaced by evil instruction ordering tricks.
/onnv-gate/usr/src/uts/common/sys/nxge/
H A Dnxge_hw.h42 #error Bit ordering not defined
/onnv-gate/usr/src/common/openssl/apps/
H A Dopenssl.cnf71 preserve = no # keep passed DN ordering
/onnv-gate/usr/src/cmd/agents/snmp/mib/
H A Ddraft-ietf-entmib-entmib-02.txt721 the agent should assign an arbitrary ordering to a given set
732 Parent-relative ordering should start from '1' and continue
734 entity. Note that this ordering may be sparse or dense,
738 ordering is only meaningful among siblings of the same
/onnv-gate/usr/src/cmd/lp/model/
H A Dnetstandard389 # sets default value for ordering of data and control files with
H A Dtsol_netstandard425 # sets default value for ordering of data and control files with
H A Dtsol_netstandard_foomatic442 # sets default value for ordering of data and control files with
/onnv-gate/usr/src/cmd/filesync/
H A DREADME166 reconciliation. The ordering is important both for correctness
/onnv-gate/usr/src/cmd/file/
H A Dmagic313 # The CPU endian architecture is determined via the ordering of the first 4 bytes
/onnv-gate/usr/src/lib/
H A DREADME.mapfiles318 to slip out of updates, or to change ordering).
/onnv-gate/usr/src/cmd/sgs/libld/common/
H A Dlibld.msg1047 @ MSG_MAP_SECINSEG "%s: %llu: section within segment ordering done on \
1155 @ MSG_MAP_SECORDER "section ordering requested, but no matching section \

12