Sugest - Externals

16 years ago by Mathias Grimm — view source — reply

unread

I want to suggest the GO include format

<?php
require
(
'utila.php',
'utilb.php',
'utilc.php',
)

the same from include

or more , without comma

<?php

require
(
'utila.php'
'utilb.php'
'utilc.php'
)

or more, withou .php
<?php

require
(
'utila',
'utilb',
'utilc',
)

the same for other to, like define..

<?php
define
(
'K_TYPE_A' => 'a',
'K_TYPE_B' => 'b'
'K_TYPE_C' => 'c'
)

with or withou comma...

--
Att.
Mathias Grimm

http://mathiasgrimm.com.br
http://phpempregos.com.br

16 years ago by johannes@schlueters.de — view source — reply

unread

I want to suggest the GO include format

<?php
require
(
'utila.php',
'utilb.php',
'utilc.php',
)

the same from include

What's te benefit, other than saving a few chars on the cost of being
more explicit. I don't see any benefit.

Doing this would mean an error to include one of these files would give
an imprecise error message. Given

<?php
require(
$a,
$b
);
?>

fails it will always tell you about an error in line 5 (basically where
the ; is)

<?php
require $a;
require $b;
?>

will give you the precise line.

Other similar issues exist.

or more , without comma

<?php

require
(
'utila.php'
'utilb.php'
'utilc.php'
)

that looks more like a typo than expected code.

or more, withou .php
<?php

require
(
'utila',
'utilb',
'utilc',
)

that makes no sense. It would have to check for two files, and why
only .php? Why not .inc or .class or whatever people are using?

the same for other to, like define..

<?php
define
(
'K_TYPE_A' => 'a',
'K_TYPE_B' => 'b'
'K_TYPE_C' => 'c'
)

with or without comma...

define() is a regular function so we'd have to make it a language
construct (which creates issues) or do some strange things to function
declarations.

Again, I see no benefit (and no, a few characters more are no trouble,
writing code is never the hard part. The hard part is maintenance ...
and a proper IDE serves quite well for saving key strokes ...)

johannes

16 years ago by Mathias Grimm — view source — reply

unread

2010/5/14 Johannes Schlüter johannes@schlueters.de
> <?php
> require
> (
> 'utila.php',
> 'utilb.php',
> 'utilc.php',
> )
    What's te benefit, other than saving a few chars on the cost
    of being
    more explicit. I don't see any benefit.
make php more productive is always good.
Less characters doesn't make anything more productive. Saving the few
characters might save a second while typing, but the additional keyword
makes ready cleaner. A line of code is read way more often than typed.

define
(
'a'=>1
'b'=>2
'c'=>3
)

its cleaner to me. like C ENUM.

enum DAY /* Defines an enumeration type */

{
saturday, /* Names day and declares a /
sunday = 0, / variable named workday with /
monday, / that type /
tuesday,
wednesday, / wednesday is associated with 3 */
thursday,
friday
} workday;

it is cleaner for everyone.
maybe the enum type could even be created for this.

there are others cases where error is imprecise

if($a==$b){

if($c==$d){...}

the error will be raised at line 3 without a precise messagem. this is
a trivial code and have imprecise message error.

Yes. So we should make it worse since it isn't perfect in one place?

there are fixes to be the error line be precise.

utila.inc will be include utila.inc.php,
utila.class will be include util.class..php

if you use utila.class without php in your project, its is a security
problem.

That's wrong.

if string dont finish with .php, .php will be included,

That breaks tons of code. and just makes life harder.

ok, maybe its not the best ideia.

forget IDE. think in a simple text editor without any resources...
php is php, IDE is IDE.

If you talk about being productive you use tools which make you
productive.

im talking about more productive. evoltion of produtivity

few character less can be good.

se one php example:
HTTP_POST_VARS => _POST

it always good write less and do more.

So we should rename all functions,too? mysql_query() is long, mq()
should work well?

no, isnt a rename..
its a new constructor of php.

mq is ambiguos, but require(..,..,..),define(..,..,..) its cleaner, not a
rename.

the main php ideia is to write less and do more,or we would be still
writing pages in ANSI C or assembly

no. That's Perl, and Perl is known as unreadable write-only language.

johannes

require(...,..,..),define(...,...) dont make php harder to read and make
easy to write.

--
Att.
Mathias Grimm

http://mathiasgrimm.com.br
http://phpempregos.com.br

16 years ago by Arvids Godjuks — view source — reply

unread

2010/5/14 Mathias Grimm mathiasgrimm@gmail.com:

2010/5/14 Johannes Schlüter johannes@schlueters.de
> <?php
> require
....

There is one thing you don't take into account.
Make an index.php and all other files .inc. Than add to web servers
configuration a deny rule for *.inc . Suddenly you improved your
security dramatically because there is only one access point for the
whole project. I use this 100% every time.

Sugest View as Markdown