Re: A non-Vim behavioural problem

On Thu, Apr 29, 2010 at 09:47:37PM -0400, Steve Bertrand wrote:
>...however, in reports, emails and/or bug notifications, it will often
>look like this:
>
> $self->function_orders();
>
> my $type = $params->{ type };
> my $data = $params->{ data };
> my $error = $params->{ error };
>
> my $vardb = ISP::Vars->new();
>
> # die right off the bat if either data is an invalid type,
> # or no $error obj was passed in
>
> if ( ! defined $error ) {
> $error = ISP::Error->new();
> $error->bad_api();
> }
>
>....which makes it difficult (ie. *very* frustrating) to review down the
>road.

Following on from Marc's reply, you might consider running your code through perltidy before committing it. By default it will convert any tabs to spaces and tidy the code for you, although you can change the default behaviour.

--

.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php