Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
References: <48C3DAD1.6030004@morningstar2.co.uk>
Message-ID:  <B9401E8C-FE13-4836-BD77-A488EC2EAE82@gmail.com>
Date:         Sun, 7 Sep 2008 23:27:45 +0930
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: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: \clist_gput_right:Nx?
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <48C3DAD1.6030004@morningstar2.co.uk>
Precedence: list
Status: R

On 07/09/2008, at 11:14 PM, Joseph Wright wrote:

> Hello,
>
> Is there a reason expl3 has
>
> \clist_put_right:Nx
> \clist_put_left:Nx
>
> but no
>
> \clist_gput_right:Nx
> \clist_gput_left:Nx
>
> when the other (non-expanded) variants are all available as gpu and  
> put
> variations?  As it stands, I have to use \clist_put_right:Nx for a
> global list: not good.

I agree. l3seq and l3tlp exhibit similar inconsistencies. Since it's  
hardly any extra code to include in the base package, I'd argue for  
extending most of these functions to support as many variants as  
reasonably possible -- and to be consistent between modules, as well.

I've got to run now, but I'll take a look at fleshing these out over  
the next couple of days.

Will