<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is creating a unit a &#8220;user&#8221; function?</title>
	<atom:link href="http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/</link>
	<description>Coding in the TeX world</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:07:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-207</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Sat, 07 Mar 2009 14:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-207</guid>
		<description>Hello Stefan,

From various things I&#039;ve been doing (LaTeX3 work, name space questions, looking at other packages, answering questions, etc.) I&#039;m pretty convinced that this type of &quot;set up&quot; macro should use design-like naming (upper- and lower-case mixed names). Hence thinking about \DeclareUnit.  The current working copy uses:

- \DeclareSIPrefix
- \DeclareSIPower
- \DeclareSIQualifier
- \DeclareSIUnit

Most users will probably never need to use these macros, and I think that the names should now be both memorable and very unlikely to clash with anything.

Joseph</description>
		<content:encoded><![CDATA[<p>Hello Stefan,</p>
<p>From various things I&#8217;ve been doing (LaTeX3 work, name space questions, looking at other packages, answering questions, etc.) I&#8217;m pretty convinced that this type of &#8220;set up&#8221; macro should use design-like naming (upper- and lower-case mixed names). Hence thinking about \DeclareUnit.  The current working copy uses:</p>
<p>- \DeclareSIPrefix<br />
- \DeclareSIPower<br />
- \DeclareSIQualifier<br />
- \DeclareSIUnit</p>
<p>Most users will probably never need to use these macros, and I think that the names should now be both memorable and very unlikely to clash with anything.</p>
<p>Joseph</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Pinnow</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-203</link>
		<dc:creator>Stefan Pinnow</dc:creator>
		<pubDate>Sat, 07 Mar 2009 10:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-203</guid>
		<description>Hi Joseph,
what about the \addunit command from the siunits package?

Best regards,
Stefan</description>
		<content:encoded><![CDATA[<p>Hi Joseph,<br />
what about the \addunit command from the siunits package?</p>
<p>Best regards,<br />
Stefan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-104</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Wed, 11 Feb 2009 19:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-104</guid>
		<description>The plan for v2 is that by default I&#039;ll only define stuff inside \SI and \si (although there will be an option to control this).  So I&#039;m also in favour of \Declare ... I&#039;m probably not going to go for \DeclareUnit as I suspect it is still too general (there are other things which are &quot;units&quot;).</description>
		<content:encoded><![CDATA[<p>The plan for v2 is that by default I&#8217;ll only define stuff inside \SI and \si (although there will be an option to control this).  So I&#8217;m also in favour of \Declare &#8230; I&#8217;m probably not going to go for \DeclareUnit as I suspect it is still too general (there are other things which are &#8220;units&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: phi</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-103</link>
		<dc:creator>phi</dc:creator>
		<pubDate>Wed, 11 Feb 2009 17:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-103</guid>
		<description>If the unit macros are undefined outside of \SI or \si, then name clashes are nearly impossible and one \DeclareUnit macro would be sufficient. On the other hand, it would not be too difficult to provide the other combinations. My suggestion in this case is \CreateUnit, \OverwriteUnit, \DeclareUnit and \ProvideUnit. I don&#039;t like names like \newcommand—they are hard to read and don&#039;t follow the usual verb–object pattern.</description>
		<content:encoded><![CDATA[<p>If the unit macros are undefined outside of \SI or \si, then name clashes are nearly impossible and one \DeclareUnit macro would be sufficient. On the other hand, it would not be too difficult to provide the other combinations. My suggestion in this case is \CreateUnit, \OverwriteUnit, \DeclareUnit and \ProvideUnit. I don&#8217;t like names like \newcommand—they are hard to read and don&#8217;t follow the usual verb–object pattern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-99</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Mon, 09 Feb 2009 08:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-99</guid>
		<description>This was broadly my thinking, to be honest.  I&#039;m not so struck on \DeclareSIunit because I think it doesn&#039;t really follow the usual &quot;rules&quot; for desgin-type macro names (should be \DeclareSIUnit, which I find hard to read).</description>
		<content:encoded><![CDATA[<p>This was broadly my thinking, to be honest.  I&#8217;m not so struck on \DeclareSIunit because I think it doesn&#8217;t really follow the usual &#8220;rules&#8221; for desgin-type macro names (should be \DeclareSIUnit, which I find hard to read).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Robertson</title>
		<link>http://www.texdev.net/2009/02/08/is-creating-a-unit-a-user-function/#comment-98</link>
		<dc:creator>Will Robertson</dc:creator>
		<pubDate>Mon, 09 Feb 2009 04:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=168#comment-98</guid>
		<description>How important do you judge it to be that users will really need the distinction between new/renew/provide ? For something this specialised, I&#039;d be inclined to stick to only using \Declare -- similar to, e.g., amsmath&#039;s \DeclareMathOperator. I&#039;d steer clear of \create, just because it&#039;s different.

Another possible option: \DeclareSIunit ?</description>
		<content:encoded><![CDATA[<p>How important do you judge it to be that users will really need the distinction between new/renew/provide ? For something this specialised, I&#8217;d be inclined to stick to only using \Declare &#8212; similar to, e.g., amsmath&#8217;s \DeclareMathOperator. I&#8217;d steer clear of \create, just because it&#8217;s different.</p>
<p>Another possible option: \DeclareSIunit ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

