On 11/8/2012 9:15 AM, Taco Hoekwater wrote:
On 11/07/2012 07:37 PM, Stephan Hennig wrote:
Am 06.07.2011 15:43, schrieb Taco Hoekwater:
On 07/04/11 09:06, Paul Isambert wrote:
The manual says you're in charge of ensuring that in
"node.insert_after(H, N, x)", N is in the list denoted by H. The thing
is, H doesn't seem to matter at all, unless it's nil:
Actually H is also useful if N is nil (that is a tail-append the list
that starts at H), but it is true that H is generally unused.
If N is known to be non-nil, e.g., a glyph node, is it save to call
node.insert_after(nil, N, x) ?
If the answer is 'Yes',
Well, yes. However I do not like the idea of reordering the
arguments, because we have quite a lot of functions with 'head'
argument, and they always come first.
indeed reordering in no option
(we could consider a two argument variant i.e. if two arguments, then
assume N, x)
Best wishes,
Taco
I propose re-ordering parameters of function
node.insert_after (and node.insert_before), so that head can be easily
left out in the function call:
function node.insert_after(<new>, <current>, <head>)
Best regards,
Stephan Hennig
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
