Lines Matching refs:components
60 url_parse::Component components[4]) {
71 components[cur_component] =
78 // Don't allow empty components (two dots in a row), except we may
102 // Fill in any unused components.
104 components[cur_component++] = url_parse::Component();
116 // out any input that is greater than 7 bits. The components are assumed
210 // The identified components. Not all may exist.
211 url_parse::Component components[4];
212 if (!FindIPv4Components(spec, host, components))
215 // Convert existing components to digits. Values up to
220 if (components[i].len <= 0)
223 spec, components[i], &component_values[existing_components]);
234 // First, process all components but the last, while making sure each fits
253 // Tell the caller how many components we saw.
285 // Helper class that describes the main components of an IPv6 input string.
330 // There can be up to 8 hex components (colon separated) in the literal.
333 // The count of hex components present. Ranges from [0,8].
363 // Scan through the input, searching for hex components, "::" contractions,
364 // and IPv4 components.
370 // (separator between hex components, or start of a contraction), or end of
379 // Don't allow empty components.
390 // Can't have more than 8 components!
412 // Colons are separators between components, keep track of where the
420 // Regular components are hex numbers. It is also possible for
440 // Verifies the parsed IPv6 information, checking that the various components
441 // add up to the right number of bits (hex components are 16 bits, while
506 // components are, the "::" contraction, and the embedded IPv4 address.
520 // Loop through each hex components, and contraction in order.
675 url_parse::Component components[4]) {
676 return DoFindIPv4Components<char, unsigned char>(spec, host, components);
681 url_parse::Component components[4]) {
682 return DoFindIPv4Components<char16, char16>(spec, host, components);
