Mark Overmeer writes: > * 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. 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!
Sure, but some people like Pod. Lots of things other than Perl 5 have been documented with POD, so lets continue to make this kind of thing easier. > And why do you want easy to remove docs? I didn't mean remove them for human (non-)consumption, but filtering them out from, say, a shell script so that what remains is a syntactically valid script which can be run in the shell. > Other languages already have their own documentation system. Why do > you expect them to use POD6? Most people won't. But that's no reason to make it hard. Smylers
