Comments on: Promoting xparse http://www.texdev.net/2010/05/22/promoting-xparse/ Coding in the TeX world Fri, 03 Feb 2012 20:29:59 +0000 hourly 1 By: Joseph Wright http://www.texdev.net/2010/05/22/promoting-xparse/#comment-2659 Joseph Wright Sun, 23 May 2010 21:45:19 +0000 http://www.texdev.net/?p=702#comment-2659 Sounds like xparse before the re-write (when there was still a lot of other "stuff" that had been thought about). Sounds like xparse before the re-write (when there was still a lot of other “stuff” that had been thought about).

]]> By: Lars Madsen http://www.texdev.net/2010/05/22/promoting-xparse/#comment-2649 Lars Madsen Sun, 23 May 2010 10:21:31 +0000 http://www.texdev.net/?p=702#comment-2649 just did a test, it seems that it has changed since the last time I worked with it. Then it was quite clear in the log that xparse (or one of the packages it loads) would alocate two writes. It does not seem to do that anymore just did a test, it seems that it has changed since the last time I worked with it. Then it was quite clear in the log that xparse (or one of the packages it loads) would alocate two writes.

It does not seem to do that anymore

]]> By: From newcommand to NewDocumentCommand at Some TeX Developments http://www.texdev.net/2010/05/22/promoting-xparse/#comment-2648 From newcommand to NewDocumentCommand at Some TeX Developments Sun, 23 May 2010 08:54:14 +0000 http://www.texdev.net/?p=702#comment-2648 [...] on from my last post, I thought it might be useful to give some simple example of how the xparse package works and why [...] [...] on from my last post, I thought it might be useful to give some simple example of how the xparse package works and why [...]

]]> By: Joseph Wright http://www.texdev.net/2010/05/22/promoting-xparse/#comment-2647 Joseph Wright Sun, 23 May 2010 08:47:50 +0000 http://www.texdev.net/?p=702#comment-2647 I can't speak for e-TeX, although I'd guess that this is because file operations have a "cost" at the OS level. On xparse, I don't follow. There should not be any reads or writes involved in xparse: can you provide an example (including \listfiles)? One thing I would add is that the I/O unit for expl3 provides a much more flexible approach to opening reads and writes than the one used by LaTeX2e. It implements a pool, so as long as programmers are sensible (closing I/O once they've finished with it) then we should have much less risk of running out. See what I've done in notes2bib, for example, where I don't need to know anything about the shipout so can have a one-shot I/O at the end of the document. I can’t speak for e-TeX, although I’d guess that this is because file operations have a “cost” at the OS level.

On xparse, I don’t follow. There should not be any reads or writes involved in xparse: can you provide an example (including \listfiles)?

One thing I would add is that the I/O unit for expl3 provides a much more flexible approach to opening reads and writes than the one used by LaTeX2e. It implements a pool, so as long as programmers are sensible (closing I/O once they’ve finished with it) then we should have much less risk of running out. See what I’ve done in notes2bib, for example, where I don’t need to know anything about the shipout so can have a one-shot I/O at the end of the document.

]]> By: Lars Madsen http://www.texdev.net/2010/05/22/promoting-xparse/#comment-2646 Lars Madsen Sun, 23 May 2010 08:42:18 +0000 http://www.texdev.net/?p=702#comment-2646 xparse can be used for very interesting things. I have one question though: Why does it allocate two writes, when in most cases those writes are not used? At least my own hacks to release them does not seem to cause problems in my use of xparse. This becomes a problem in large projects where one is running out of writes. Why was the number of writes/reads not increased by etex with the rest of things? xparse can be used for very interesting things. I have one question though:

Why does it allocate two writes, when in most cases those writes are not used? At least my own hacks to release them does not seem to cause problems in my use of xparse.

This becomes a problem in large projects where one is running out of writes.

Why was the number of writes/reads not increased by etex with the rest of things?

]]>