Perl vs. PHP - Revision history

Woozle: tweaks

2007-01-27T17:40:27Z

tweaks

← Older revision		Revision as of 17:40, 27 January 2007
Line 1:		Line 1:
	[[computing]]: [[software]]: [[Perl]]/[[PHP]]: [[~~Perl vs.~~ PHP]]		==Navigation==
			{\|
			\|-
			\| colspan=2 rowspan=2 valign=middle \| [[computing]]: [[software]]: \|\| [[Perl]]: \|\| rowspan=2 valign=middle \| [[Perl vs. PHP]]
			\|-
			\| [[PHP]]:
			\|}
	{{seedling}}		{{seedling}}
	==Overview==		==Overview==
Line 7:		Line 13:
	==Links==		==Links==
	* [http://tnx.nl/php PHP in contrast to Perl]		* [http://tnx.nl/php PHP in contrast to Perl]
	* [http://www.cs.wcupa.edu/~rkline/perl2php/ Perl/Php Translation]		* [http://www.cs.wcupa.edu/~rkline/perl2php/ Perl/Php Translation]: a handy reference for how to do useful stuff in either language, even if you're not trying to port from one to the other

	==Object-Oriented Programming==		==Object-Oriented Programming==
	[[object-oriented programming]], or OOP, was a late addition to both languages, but it's a bit easier to use in PHP. (Perl's implementation ~~may be more powerful~~, ~~but it's not at all clear how~~.) A comparison:		[[object-oriented programming]], or OOP, was a late addition to both languages, but it's a bit easier to use in PHP. (Perl's implementation is being dramatically improved for Perl 6, in development as of January 2007.) A comparison:
	{\|		{\|
	\|-		\|-

Woozle: /* Links */ translation

2007-01-27T17:27:21Z

Links: translation

← Older revision		Revision as of 17:27, 27 January 2007
Line 7:		Line 7:
	==Links==		==Links==
	* [http://tnx.nl/php PHP in contrast to Perl]		* [http://tnx.nl/php PHP in contrast to Perl]
			* [http://www.cs.wcupa.edu/~rkline/perl2php/ Perl/Php Translation]

	==Object-Oriented Programming==		==Object-Oriented Programming==
	[[object-oriented programming]], or OOP, was a late addition to both languages, but it's a bit easier to use in PHP. (Perl's implementation may be more powerful, but it's not at all clear how.) A comparison:		[[object-oriented programming]], or OOP, was a late addition to both languages, but it's a bit easier to use in PHP. (Perl's implementation may be more powerful, but it's not at all clear how.) A comparison:

Woozle: /* Notes */ PHP::Strings

2006-12-06T14:22:09Z

Notes: PHP::Strings

← Older revision		Revision as of 14:22, 6 December 2006
Line 40:		Line 40:

	==Notes==		==Notes==
	* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, ~~thus making it easier to gracefully port~~ a ~~project from one to the other~~		===Porting from PHP to Perl===
			* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code
			* [http://search.cpan.org/~spoon/PHP-Strings/Strings.pm PHP::Strings]: a [[Perl]] module that implements most of the PHP String functions (those which are not implemented are generally trivial, and are stubbed with a message explaining this)

Woozle: /* Object-Oriented Programming */ updates

2006-10-23T19:45:47Z

Object-Oriented Programming: updates

← Older revision		Revision as of 19:45, 23 October 2006
Line 13:		Line 13:
	! bgcolor="#eeeeee" \| characteristic \|\| [[Perl]] \|\| [[PHP]]		! bgcolor="#eeeeee" \| characteristic \|\| [[Perl]] \|\| [[PHP]]
	\|-		\|-
	\| bgcolor="#eeeeee" \| class files \|\| one class per file \|\| multiple classes per file		\| bgcolor="#eeeeee" \| class files \|\| typically one class per file,<br>but multiple classes are possible \|\| multiple classes per file
	\|-		\|-
	\| bgcolor="#eeeeee" \| class initialization code \|\|		\| bgcolor="#eeeeee" \| class initialization code \|\|
Line 37:		Line 37:
	* On the surface, PHP's identifier-within-class syntax seems more complicated, but it made intuitive sense to me ({{woozle}}) except possibly for the issue of which identifiers get dollar-signs and which don't (which is even more complicated in Perl)... although I don't see why PHP needs both "this" and "self" when there's the "->" vs. "::" to disambiguate dynamic from static (but again, this is a minor annoyance and much less confusing than many aspects of Perl's OOP syntax).		* On the surface, PHP's identifier-within-class syntax seems more complicated, but it made intuitive sense to me ({{woozle}}) except possibly for the issue of which identifiers get dollar-signs and which don't (which is even more complicated in Perl)... although I don't see why PHP needs both "this" and "self" when there's the "->" vs. "::" to disambiguate dynamic from static (but again, this is a minor annoyance and much less confusing than many aspects of Perl's OOP syntax).
	* In Perl, any string inside delimiters (such as [], {}, ()) is assumed to be a string literal if it does not begin with $ and does not contain any delimiters. (This is a rough guess at the actual rules, which may be more complicated.) For this reason, some examples of class initialization show the field names without quotes, e.g. "$self->{FIELDNAME} = 'value';", which can be more understandably written as "$self->{'FIELDNAME'} = default;".		* In Perl, any string inside delimiters (such as [], {}, ()) is assumed to be a string literal if it does not begin with $ and does not contain any delimiters. (This is a rough guess at the actual rules, which may be more complicated.) For this reason, some examples of class initialization show the field names without quotes, e.g. "$self->{FIELDNAME} = 'value';", which can be more understandably written as "$self->{'FIELDNAME'} = default;".
			* Apparently the OOP syntax in Perl 6 (currently in development) is much improved and more intuitive; the OOP syntax in Perl 5 is more like grafting OOP onto a basically procedural language.

	==Notes==		==Notes==
	* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other		* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other

Woozle: /* Object-Oriented Programming */ fieldnames are normally in quotes

2006-10-20T18:14:33Z

Object-Oriented Programming: fieldnames are normally in quotes

← Older revision		Revision as of 18:14, 20 October 2006
Line 17:		Line 17:
	\| bgcolor="#eeeeee" \| class initialization code \|\|		\| bgcolor="#eeeeee" \| class initialization code \|\|
	my $self = {};		my $self = {};
	$self->{FIELDNAME} = ''default'';		$self->{'FIELDNAME'} = ''default'';
	...		...
	{{perlfunc\|bless}}($self);		{{perlfunc\|bless}}($self);

Woozle: /* OOP Notes */ explanations, based on Tene's answers

2006-10-20T18:13:49Z

OOP Notes: explanations, based on Tene's answers

← Older revision		Revision as of 18:13, 20 October 2006
Line 33:		Line 33:
	\|}		\|}
	===OOP Notes===		===OOP Notes===
	* In Perl~~, it~~'s ~~not quite clear what's going on with~~ the ~~field names~~. ~~Is FIELDNAME implicitly created as a constant in this context?~~		* In class methods, the object itself is an implicit first argument; the {{perlfunc\|shift}} function uses the @_ magic variable by default, effectively retrieving the object reference.
			* The Perl {{perlfunc\|bless}} function causes the package's functions to be bound into the [[hashref]] object (probably creates a [[virtual method table\|VMT]] for it); without being blessed, the object is just a normal hashref.
	* On the surface, PHP's identifier-within-class syntax seems more complicated, but it made intuitive sense to me ({{woozle}}) except possibly for the issue of which identifiers get dollar-signs and which don't (which is even more complicated in Perl)... although I don't see why PHP needs both "this" and "self" when there's the "->" vs. "::" to disambiguate dynamic from static (but again, this is a minor annoyance and much less confusing than many aspects of Perl's OOP syntax).		* On the surface, PHP's identifier-within-class syntax seems more complicated, but it made intuitive sense to me ({{woozle}}) except possibly for the issue of which identifiers get dollar-signs and which don't (which is even more complicated in Perl)... although I don't see why PHP needs both "this" and "self" when there's the "->" vs. "::" to disambiguate dynamic from static (but again, this is a minor annoyance and much less confusing than many aspects of Perl's OOP syntax).
	* ~~I ''still'' don't understand what~~ {~~{perlfunc\|bless}~~} does. ({~~{woozle~~}~~}) Or~~ {~~{perlfunc\|shift}~~}.		* In Perl, any string inside delimiters (such as [], {}, ()) is assumed to be a string literal if it does not begin with $ and does not contain any delimiters. (This is a rough guess at the actual rules, which may be more complicated.) For this reason, some examples of class initialization show the field names without quotes, e.g. "$self->{FIELDNAME} = 'value';", which can be more understandably written as "$self->{'FIELDNAME'} = default;".

	==Notes==		==Notes==
	* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other		* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other

Woozle: /* Links */ OOP comparison

2006-10-20T16:45:39Z

Links: OOP comparison

@@ Line 7: / Line 7: @@
 ==Links==
 * [http://tnx.nl/php PHP in contrast to Perl]
 ==Notes==
 * [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other

Woozle: /* Links */ PHP::Interpreter

2006-10-12T00:03:39Z

Links: PHP::Interpreter

← Older revision		Revision as of 00:03, 12 October 2006
Line 7:		Line 7:
	==Links==		==Links==
	* [http://tnx.nl/php PHP in contrast to Perl]		* [http://tnx.nl/php PHP in contrast to Perl]
			==Notes==
			* [http://search.cpan.org/~gschloss/PHP-Interpreter-1.0.1/lib/PHP/Interpreter.pm PHP::Interpreter]: a [[Perl]] module for running [[PHP]] code, thus making it easier to gracefully port a project from one to the other

Woozle: seedling; overview section; navbar

2006-06-29T15:01:40Z

seedling; overview section; navbar

← Older revision		Revision as of 15:01, 29 June 2006
Line 1:		Line 1:
			[[computing]]: [[software]]: [[Perl]]/[[PHP]]: [[Perl vs. PHP]]
			{{seedling}}
			==Overview==
	[[Perl]] and [[PHP]] are often compared with each other, largely due to their mutual popularity for web site design. The general consensus seems to be that people use PHP because it was invented specifically for creating web pages, whereas Perl has a lot of other uses as well — or, in other words, people use PHP because they don't know any better, and people who know better use Perl.		[[Perl]] and [[PHP]] are often compared with each other, largely due to their mutual popularity for web site design. The general consensus seems to be that people use PHP because it was invented specifically for creating web pages, whereas Perl has a lot of other uses as well — or, in other words, people use PHP because they don't know any better, and people who know better use Perl.

Woozle at 01:48, 27 February 2006

2006-02-27T01:48:19Z

New page

[[Perl]] and [[PHP]] are often compared with each other, largely due to their mutual popularity for web site design. The general consensus seems to be that people use PHP because it was invented specifically for creating web pages, whereas Perl has a lot of other uses as well — or, in other words, people use PHP because they don't know any better, and people who know better use Perl.

Unfortunately, this apparently does nothing to prevent the use of PHP in such heavily-used, highly-developed applications as [[MediaWiki]] and [[Drupal]].
==Links==
* [http://tnx.nl/php PHP in contrast to Perl]