[Quoting Autrijus Tang, on March 28 2003, 20:16, in "Re: Module submissio"]
> After your remarks that raised your module to the 'software framework'
> level required by a top-level CPAN name, I see that OODoc is an adequate
> name and am willing to approve it, if no better suggestions comes up in
>
On Fri, Mar 28, 2003 at 12:08:22PM +0100, Mark Overmeer wrote:
> I think were are getting into a syntax debate for one of the
> documentation parsers which is implemented for OODoc. Debates
> about syntax are about as subjective as those about coding styles.
I did not know that you plan to implem
* Johan Vromans ([EMAIL PROTECTED]) [030328 12:38]:
> [Quoting Mark Overmeer, on March 28 2003, 12:25, in "Re: Module submissio"]
> > "Information" does not cover the processing, which the module does.
>
> Right, I was confusing the information with the processing.
> MDS (Mark's Document System)
[Quoting Mark Overmeer, on March 28 2003, 12:25, in "Re: Module submissio"]
> > MDI (Mark's Document Information).
> > XDI (Extended/Extensible Document Information).
>
> "Information" does not cover the processing, which the module does.
Right, I was confusing the information with the processing
* Johan Vromans ([EMAIL PROTECTED]) [030328 12:15]:
> > Other suggestions?
>
> MDI (Mark's Document Information).
> XDI (Extended/Extensible Document Information).
"Information" does not cover the processing, which the module does.
"X" from "XDI" is loaded with a relation to "XML", which is not
> Other suggestions?
MDI (Mark's Document Information).
XDI (Extended/Extensible Document Information).
-- Johan
* Johan Vromans ([EMAIL PROTECTED]) [030328 11:15]:
> The =begin, =end and =for directives as recognized by POD parsers[1]
> are designed to add specific extensions to POD. However, when you only
> use the extensions then POD reduces to the bare mechanism to embed
> non-perl information in perl pro
On Fri, Mar 28, 2003 at 11:15:00AM +0100, Johan Vromans wrote:
> Technically, this is true. But is this POD? Would you call this C:
>
>int foo(int bar) {
> _asm("...");
> _asm("...");
> _asm("...");
> _asm("...");
>}
Why, of course yes. There are plenty of perl progra
[Quoting Autrijus Tang, on March 28 2003, 16:14, in "Re: Module submissio"]
> Well in fact, sure:
>
> =for docbook
>
>
>
>
Technically, this is true. But is this POD? Would you call this C:
int foo(int bar) {
_asm("...");
_asm("...");
_asm("...");
On Fri, Mar 28, 2003 at 08:16:29AM +0100, Mark Overmeer wrote:
> I don't think that the POD parser can handle this
>
> =docbook
>
>
>
>
>
>
> =cut
Well in fact, sure:
=for docbook
=cut
For example, pod2html already recognizes "=for html" bl
* Autrijus Tang ([EMAIL PROTECTED]) [030328 04:57]:
> Is there anything in POD explicitly forbidden or incompatible with
> OODoc? If such conflicts necessarily exist, I'd be happy to rescind
> my disagreement.
OODco (or whatever it will be called) has three phases:
1) parsing
2) inheritance r
On Thu, Mar 27, 2003 at 05:56:38PM +0100, Johan Vromans wrote:
> Hmm. Slightly simplified, perl ignores everything between (and
> including) a line that starts with '=', and a line that reads '=cut'.
> POD is one application that makes use of this to allow embedded
> documentation in perl programs.
On Thu, Mar 27, 2003 at 08:11:04AM +0100, Mark Overmeer wrote:
> > Personally, the name 'Pod::OO' sounds much more encouraging for other
> > module authors to try on (since it implies that it is compatible with
> > the POD syntax).
>
> That's one good point for POD::OO. That's probably the reason
Autrijus Tang <[EMAIL PROTECTED]> writes:
> and it seems to me that this implies that OODoc is an extension that
> inherits the POD syntax, instead of something entirely different.
Hmm. Slightly simplified, perl ignores everything between (and
including) a line that starts with '=', and a line th
* Autrijus Tang ([EMAIL PROTECTED]) [030326 18:25]:
> On Wed, Mar 26, 2003 at 06:13:24PM +0100, Arthur Bergman wrote:
> I think Pod::OO or Pod::OODoc is less vague and more helpful for what
> this module does. As MARKOV states:
>
> POD is a visual markup language, and therefore information i
On Wed, Mar 26, 2003 at 06:13:24PM +0100, Arthur Bergman wrote:
> >Last week I tried to get response from this modules list, but there
> >was none. I know you are all very busy, but I can't wait too much
> >longer. Therefore, I now ask for the name space officially.
>
> I am not so sur
On onsdag, mar 26, 2003, at 18:06 Europe/Stockholm, Perl Authors Upload
Server wrote:
Last week I tried to get response from this modules list, but there
was none. I know you are all very busy, but I can't wait too much
longer. Therefore, I now ask for the name space officially.
S
The following module was proposed for inclusion in the Module List:
modid: OODoc
DSLIP: bdpOp
description: Object Oriented documentation generator
userid: MARKOV (Mark Overmeer)
chapterid:2 (Perl_Core_Modules)
communities:
podpeople and German Perl Workshop
18 matches
Mail list logo
