2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
This rule allows banning certain PHP functions.
2021-04-28 18:08:03 +02:00
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2021-04-28 16:49:39 +02:00
Given a parameter of ``++foo++`` for this rule:
2022-02-04 17:28:24 +01:00
[source,php]
2021-04-28 16:49:39 +02:00
----
$arr=array("apple", "pear","banana");
echo foo($arr); // Noncompliant
----
2021-04-28 18:08:03 +02:00
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== Message
Remove this use of the "xxx" function.
=== Parameters
.functions
****
Comma-separated list of disallowed functions
****
2021-09-20 15:38:42 +02:00
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
2023-05-25 14:18:12 +02:00
=== on 19 Sep 2014, 15:16:31 Freddy Mallet wrote:
@Ann, instead of providing a template rule, I would specialize this rule : "Alias functions kept in PHP to preserve a backward compatibility should not be used". Or we could imagine to provide two rules :
* a template rule without any default value
* a specialized rule targeting alias functions
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]