Simon Cozens wrote: > Can you give me an example that is i) useful > and ii) reasonably obvious to the untrained eye? If not, I humbly suggest it > has little business being in the "blue-collar language" we call Perl. Rather than head off down this time-wasting tangent yet again, I refer readers to the archived discussions of RFC28. Suffice it to say that, contrary to some opinions, OO and FP are useful to more than just CS graduates. Part of Perl being Perl is being something greater than a lowest common denominator. -- John Porter
- Re: Apoc2 - <STDIN> concerns John Porter
- Re: Apoc2 - <STDIN> concerns Simon Cozens
- Re: Apoc2 - <STDIN> concerns Larry Wall
- Re: Apoc2 - <STDIN> concerns John Porter
- Re: Apoc2 - <STDIN> concerns Dan Sugalski
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns Dan Sugalski
- Re: Apoc2 - <STDIN> concerns John Porter
- Re: Apoc2 - <STDIN> concerns Simon Cozens
- Re: Apoc2 - <STDIN> concerns Dan Sugalski
- Re: Apoc2 - <STDIN> concerns John Porter
- Re: Apoc2 - <STDIN> concerns Simon Cozens
- Re: Apoc2 - <STDIN> concerns David L. Nicol
- Re: Apoc2 - <STDIN> concerns David L. Nicol
- Re: Apoc2 - <STDIN> concerns John Porter
- Re: Apoc2 - <STDIN> concerns Simon Cozens
- Re: Apoc2 - <STDIN> concerns Dan Sugalski
- Re: Apoc2 - <STDIN> concerns Larry Wall
- Re: Apoc2 - <STDIN> concerns David L. Nicol
- Re: Apoc2 - <STDIN> concerns Damian Conway
- Re: Apoc2 - <STDIN> concerns Dave Storrs