Searched refs:implications (Results 1 – 25 of 111) sorted by relevance
12345
389 auto implications = implications_.equal_range(implied_name); in Parse() local390 for (auto it = implications.first; it != implications.second; ++it) { in Parse()
27 INPUT chain is not advised unless the implications are well
14 This option therefore has security implications when used to match traffic being
246 self.implications = function implications (argv) { function
18 you will need to conduct a thorough licensing review to determine the overall implications of
3 … practice to avoid using `eval()`. There are security and performance implications involved with d…
12 This is because these types can be mutated and carry with them more complex implications about thei…
50 implications of this feature are discussed in the GL_KHR_no_error
56 server. This has privacy implications and may also have performance implications
60 implications of this feature are discussed in the GL_KHR_no_error
66 of cryptographic principles and understand the implications of your changes.
67 the implications of many of the regular expressions; as one example,
108 implications as the external entity expansion issue.
80 I'll discuss this difference and its implications in detail later.
57 Please consult a legal representative if you do not understand the implications
73 support have any implications for how EGL devices and outputs are
71 support have any implications for how EGL devices and outputs are
141 security implications.452 understand its implications.475 should understand its implications.
78 implications about race, gender, religion, political orientation or anything
133 potential performance implications. For implementations which have an
160 3. Are there any implications on the framebuffer completeness check?
137 Total implications: