MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <87r6ki4t10.fsf@buckbeak.hogwarts>
Message-ID:  <18173.21078.356751.244461@morse.mittelbach-online.de>
Date:         Fri, 28 Sep 2007 21:13:26 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: name clash \iow_newline
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <87r6ki4t10.fsf@buckbeak.hogwarts>
Precedence: list
Status: R

Hi Andreas,

 > There is a name clash between l3io and l3messages. l3io  defines
 > a \iow_newline: (with colon), whereas l3messages requires a
 > \iow_newline (without colon).
 > 
 > I am not sure if it should be a function or a variable.

i think of it as a function though those things are a bit "matter of
opinion". Basically variables (other than tlps) cannot be used in the input
stream by themselves. tlps are different as they acknowlegde the fact that TeX
operates on token streams and tlps are simply containers for parts of the
stream

but it is interesting to look at the history (opinions change over time)
... at one stage it was \c_iow_newline .. then .. \iow_newline: ... then ...


 > * Since \err_newline: is a function, \iow_newline: should be
 >   a function, too.

i think it should be \iow_newline: and the documentation and code updated

cheers
frank

advance warning: I plan to clean up the names used for certain functions in
l3iow as they are not really fully consistent (probably in 4 weeks) --- will
send out proposal for changes then for those who are interested.