Re: POD formatter version comments

[email protected] (Shawn H Corey) Fri, 15 Mar 2024 12:45:29 -0400
Newsgroups	perl.pod-people
Message-ID	<[email protected]>
--------------qbx9fMNnD7LtIqkIzLZGmO8N
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 2024-03-15 12:44, Russ Allbery wrote:
> Shawn H Corey<[email protected]>  writes:
>
>> I think it should be an option. Sometimes it is necessary to know that a
>> change in appearance is caused by changes to a module and not to the
>> generating document.
> Do we need to explicitly state that it's an option, or would removing the
> requirement to always do it still be okay?  The way I was thinking of it
> is that what formatters put into comments is generally up to them; by
> default, they *can* include anything they want.  Removing the requirement
> thus just leaves the decision unconstrained.

I'm not sure what you're saying. If it's an option, then it is 
automatically not a requirement. Unless you mean what information to 
include is the requirement. In which case, having a standard would be nice.

-- 
𝑆𝒉𝒂𝒘𝒏 𝐻 𝐶𝒐𝒓𝒆𝒚 🇨🇦

--------------qbx9fMNnD7LtIqkIzLZGmO8N
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 2024-03-15 12:44, Russ Allbery
      wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:[email protected]">
      <pre class="moz-quote-pre" wrap="">Shawn H Corey <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">&lt;[email protected]&gt;</a> writes:

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">I think it should be an option. Sometimes it is necessary to know that a
change in appearance is caused by changes to a module and not to the
generating document.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
Do we need to explicitly state that it's an option, or would removing the
requirement to always do it still be okay?  The way I was thinking of it
is that what formatters put into comments is generally up to them; by
default, they *can* include anything they want.  Removing the requirement
thus just leaves the decision unconstrained.
</pre>
    </blockquote>
    <br>
    I'm not sure what you're saying. If it's an option, then it is
    automatically not a requirement. Unless you mean what information to
    include is the requirement. In which case, having a standard would
    be nice.<br>
    <pre class="moz-signature" cols="72">-- 
𝑆𝒉𝒂𝒘𝒏 𝐻 𝐶𝒐𝒓𝒆𝒚 🇨🇦</pre>
  </body>
</html>

--------------qbx9fMNnD7LtIqkIzLZGmO8N--