> Consider this (upcoming) Perl6 code:
>
> sub foo {
> "Snarf the frobnitzers if x > 0.1";
> my $x = shift;
> # ...
> }
Have you guys totally missed the discussions on multi-line comments?
I argued for qc//, as in
sub foo {
qc(Snarf the frobnitzers if x > 0.1);
my $x = shift;
Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
> On Sun, Aug 06, 2000 at 12:41:50AM +0300, Ariel Scolnicov wrote:
[...]
> > Have you looked at the documentation that SWIG auto-generates?
>
> Nope. Can you give a quick summary?
SWIG is a tool for interfacing C (and C++ and Fortran and ...) cod
On Sun, Aug 06, 2000 at 12:41:50AM +0300, Ariel Scolnicov wrote:
> Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > > Another alternative would be Javadoc / doxygen / ... style comments
> > > (say #@ introduces a comment to be extracted).
> >
> > Yuk. More magic to remember. Me h
Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
[...]
> > Another alternative would be Javadoc / doxygen / ... style comments
> > (say #@ introduces a comment to be extracted).
>
> Yuk. More magic to remember. Me hate.
What magic? The program that does the documentation isn't going to be
cal
On Sun, Aug 06, 2000 at 12:20:54AM +0300, Ariel Scolnicov wrote:
> Lisp calls this sort of thing a "documentation string". One nice
Yes. The (dormant) LISP programmer in me winces for not mentioning
that as a reference.
> thing about the Lisp syntax is that it works even if the Lisp doesn't
>
Lisp calls this sort of thing a "documentation string". One nice
thing about the Lisp syntax is that it works even if the Lisp doesn't
support docstrings!
We can also do this. Consider this (upcoming) Perl6 code:
sub foo {
"Snarf the frobnitzers if x > 0.1";
my $x = shift;
# ...
}
It is
This and other RFCs are available on the web at
http://tmtowtdi.perl.org/rfc/
=head1 TITLE
Bring Documentation Closer To Whatever It Documents
=head1 VERSION
Maintainer: Jarkko Hietaniemi <[EMAIL PROTECTED]>
Date: 05 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 44
=
