From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: CPerl Indentation after subs with print in their names
Date: Wed, 28 Nov 2007 20:05:33 +1100 [thread overview]
Message-ID: <87tzn6yc2q.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 85zlx0hzph.fsf@usenet.my.skamphausen.de
Stefan Kamphausen <skampi@gmx.net> writes:
> Hi Ilya,
>
> Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
>
>>> Nevertheless, it was wasted time on my side (comparing those files)
>>> and on yours (writing posts) which could have been saved if there were
>>> some comments at the beginning of the file that explained the way
>>> things are.
>>
>> Ha, I see you presume people would read what is "at the beginning of
>> the file"! And where you think this "beginning" is, before/after
>> license/changelog, or where?
>
> Can't tell. I won't even assume that other people read all that, but
> /I/ do and I always write my stuff as if others would, too :-)
>
> Hm, let's see ... there is this comment:
>
> ;; DO NOT FORGET to read micro-docs (available from `Perl' menu) <<<<<<
> ;; or as help on variables `cperl-tips', `cperl-problems', <<<<<<
> ;; `cperl-praise', `cperl-speed'. <<<<<<
>
> Somewhere close to that would be a good idea maybe. Or it could be a
> micro-doc itself. cperl-development or cperl-versions or
> cperl-maintenance or something like that.
>
>> [If you can agree on that, I put it into my TODO ;-]
>
> :-)
>
> Regards,
> Stefan
I have to say I agree with Stefan's point here. After quite a few years of
using cperl, I can say that almost without exception, everytime I've run
into problems, replacing the provided version with a newer one from Ilya's
site fixes the issue. However, it can be difficult to tell which version is
the later one (though I think there is more info in the file on this than
there use to be - I do remember being very confused in the beginning).
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2007-11-28 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 16:43 CPerl Indentation after subs with print in their names Stefan Kamphausen
2007-11-23 8:41 ` Ilya Zakharevich
2007-11-23 9:40 ` Stefan Kamphausen
2007-11-23 23:19 ` Ilya Zakharevich
2007-11-26 8:21 ` Stefan Kamphausen
2007-11-26 23:05 ` Ilya Zakharevich
2007-11-27 8:14 ` Stefan Kamphausen
2007-11-28 9:05 ` Tim X [this message]
2007-12-16 18:41 ` David Combs
2007-12-16 20:21 ` Ilya Zakharevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tzn6yc2q.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).