Mark Koopman <[EMAIL PROTECTED]> writes:
> > On Fri, 09 Feb 2001 12:06:12 -0500, Ken Fox wrote:
> >
> >
> > That may work for C, but not for Perl.
> >
> > sub test {
> > my($foo, $bar, %baz);
> > ...
> > return \%baz;
> > }
> >
> > You may notice that only PART
Simon Cozens <[EMAIL PROTECTED]> writes:
> On Fri, Feb 09, 2001 at 04:14:34PM -0800, Mark Koopman wrote:
> > > sub test {
> > > my($foo, $bar, %baz);
> > > ...
> > > return \%baz;
> > > }
> > are we considering to deprecate this type of bad style
>
> What bad style?
Well,
On Sat, 10 Feb 2001, Branden wrote:
> Another advantage I see on tar and gzip is that they are used by GNU, so I'm
> pretty sure there probably wouldn't be any licensing issues, and I'm not
> quite sure .zip doesn't use LZW, the same compression method of GIF...
Zip uses the same compress method
At 01:05 AM 2/10/2001 +0100, Bart Lateur wrote:
>On Fri, 09 Feb 2001 12:06:12 -0500, Ken Fox wrote:
> > 2. Work proportional to live data, not total data. This is hard to
> >believe for a C programmer, but good garbage collectors don't have
> >to "free" every allocation -- they just have t
Jarkko Hietaniemi wrote:
> On Fri, Feb 09, 2001 at 06:46:26PM -0200, Branden wrote:
> > Jarkko Hietaniemi wrote:
> > > Whatever we do I would much prefer being package format agnostic
> > > instead of tying ourselves too tightly with some single format.
> > Any ideas on how to do that? Without bre
Actually, I'm starting to like .tgz. With .tgz you wouldn't be able to run
the program without extracting the archive, but if you store the archive as
.tar, there would be no problem. .tgz could be used for network
transmission, and the archive could either be installed or stored as a .tar
in a st
On Fri, Feb 09, 2001 at 04:14:34PM -0800, Mark Koopman wrote:
> > sub test {
> > my($foo, $bar, %baz);
> > ...
> > return \%baz;
> > }
> are we considering to deprecate this type of bad style
What bad style?
--
DESPAIR:
It's Always Darkest Just Before it Gets
Damian Conway <[EMAIL PROTECTED]> writes:
> sub {
> ...
> return $yadda_yadda;
> }
> always { close F }
Let's try not to fall into the Java trap.
If exception handling gets too wordy, programmers will try to reduce
the overhead by combining many stat
