> brian d foy writes:
>> I doubt other languages will want to deal with this situation.
* Smylers ([EMAIL PROTECTED]) [070616 08:44]:
> With these new Pod rules it's possible to entirely remove Pod from a
> file without knowing _anything_ about the host language. (It could
> straightforwardly be done as an editor macro, for example.) That
> permits Pod to be used to document just about anything; all you need to
> allow it is a filter that strips off all Pod before you do anything else
> with the file.
And then the main point: if you write documentation which is not
related to Perl6 coding itself, do we really need to create just
another text processor? There are already so many sofisticated
text processors available!
Well, ok, if you "get it for free", like with POD(5), then take
that opportunity. But if the life of ordinary programmers who write
documentation is complicated just to provide this feature, we are IMO
on the wrong path.
And why do you want easy to remove docs? Perl6 is even nicer: you can
distribute it compiled; no program text and no docs! Docs in code
files are much less of a "burden" than in Perl5, so the need to strip
them from the code has deminished.
> If Pod were to take notice of the host language's context throughout the
> file then this would not be possible: every language which wished to
> have Pod support would require its own Pod parser embedded within the
> languge parser. _That_ is orders of magnitude more complex than the
> simplicity of filtering off all Pod first, and strikes me as something
> other languages are much less likely to be bothered to do.
Other languages already have their own documentation system. Why do you
expect them to use POD6? Why should we design POD6 with this endlessly
open requirement in mind? Let's rule the World!
All I try to achieve is the best possible set of documentation for
end-users: consistent in structure and correct in content. To achieve
this, I wish to keep the freedom and avoid the anacharchy. Correctness
automatically improves where redundancy is removed. But that requires
a closer doc/code entanglement than a lot of the experienced Perl people
like (==are used to).
--
MarkOv
------------------------------------------------------------------------
Mark Overmeer MSc MARKOV Solutions
[EMAIL PROTECTED] [EMAIL PROTECTED]
http://Mark.Overmeer.net http://solutions.overmeer.net
