LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Thu, 21 Aug 2014 22:42:57 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=UTF-8
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (19 lines)
On 20/08/2014 01:23, Allred, Sean wrote:
> I've drawn up a syntax proposal
> <> (as
> an Org file) on GitHub:

One thing I think to consider is the lesson of LaTeX(2e) in that a small
number of positional-based mandatory arguments work well as a user.
That's something I'd certainly expect to see in any new code too.

The issue with mixing up mandatory and optional arguments in an
object/template set up is that this then looks less clear (how many
arguments must a TeX-like document-level interface require?). Almost
certainly the number of truly *required* arguments will remain small,
and while the case that a design should not be limited by TeX is quite
true, and the same time a design interface that fundamentally fails to
translate to a TeX-based user layer is a problem too.
Joseph Wright