Utils::absolutizePath() - Code Metrics - jkuchar/BigFileTools - Measure and Improve Code Quality continuously with Scrutinizer

Utils::absolutizePath() A
last analyzed 2016-04-27 16:24 UTC

↳ Parent: Utils

Complexity

Conditions	2
Paths	2

Size

Total Lines	12
Code Lines	5

Duplication

Lines	0
Ratio	0 %

Importance

Changes	2
Bugs	0	Features	0

Metric	Value
dl	0
loc	12
c	2
b	0
f	0
rs	9.4285
cc	2
eloc	5
nc	2
nop	1

<?php
/**
 * Created by PhpStorm.
 * User: jkuchar1
 * Date: 31.1.2016
 * Time: 16:49
 */

namespace BigFileTools;

/**
 * Class Utils
 * @package BigFileTools
 * @internal
 */
class Utils
{
	/**
	 * Converts relative path to absolute
	 * @param string $path relative path
	 * @return string Absolute path
	 * @throws Exception
	 * @internal
	 */
	static function absolutizePath($path)

	{

		$path = realpath($path);
		if(!$path) {
			// TODO: use hack like http://stackoverflow.com/questions/4049856/replace-phps-realpath or http://www.php.net/manual/en/function.realpath.php#84012
			//       probably as optional feature that can be turned on when you know, what are you doing

			throw new Exception("Not possible to resolve absolute path.");
		}
		return $path;
	}

	/**
	 * @return bool
	 * @internal
	 */
	static function isPlatformWith32bitInteger() {

		return (string)PHP_INT_MAX === "2147483647"; // (2^31-1)

	}

	/**
	 * @return bool
	 * @internal
	 */
	static function isPlatformWith64bitInteger() {

		return (string)PHP_INT_MAX === "9223372036854775807"; // (2^63-1)

	}

}

1			<?php
2			/**
3			* Created by PhpStorm.
4			* User: jkuchar1
5			* Date: 31.1.2016
6			* Time: 16:49
7			*/
8
9			namespace BigFileTools;
10
11			/**
12			* Class Utils
13			* @package BigFileTools
14			* @internal
15			*/
16			class Utils
17			{
18			/**
19			* Converts relative path to absolute
20			* @param string $path relative path
21			* @return string Absolute path
22			* @throws Exception
23			* @internal
24			*/
25			static function absolutizePath($path)
			0 ignored issues – show Best Practice introduced 2016-02-05 18:32 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
26			{
27
28			$path = realpath($path);
29			if(!$path) {
30			// TODO: use hack like http://stackoverflow.com/questions/4049856/replace-phps-realpath or http://www.php.net/manual/en/function.realpath.php#84012
31			// probably as optional feature that can be turned on when you know, what are you doing
32
33			throw new Exception("Not possible to resolve absolute path.");
34			}
35			return $path;
36			}
37
38			/**
39			* @return bool
40			* @internal
41			*/
42			static function isPlatformWith32bitInteger() {
			0 ignored issues – show Best Practice introduced 2016-02-05 18:32 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
43			return (string)PHP_INT_MAX === "2147483647"; // (2^31-1)
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-05 18:32 UTC by Report Bug Copy Issue Report `75%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
44			}
45
46			/**
47			* @return bool
48			* @internal
49			*/
50			static function isPlatformWith64bitInteger() {
			0 ignored issues – show Best Practice introduced 2016-02-05 18:32 UTC by Report Bug Copy Issue Report It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
51			return (string)PHP_INT_MAX === "9223372036854775807"; // (2^63-1)
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-05 18:32 UTC by Report Bug Copy Issue Report `75%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
52			}
53
54			}

jkuchar / BigFileTools

Utils::absolutizePath() A last analyzed 2016-04-27 16:24 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

Utils::absolutizePath() A
last analyzed 2016-04-27 16:24 UTC