Path: ...!npeer.as286.net!npeer-ng0.as286.net!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Christian Gollwitzer Newsgroups: comp.lang.tcl Subject: Re: where is the TCL "macro" command ? Date: Fri, 28 Jun 2024 20:58:04 +0200 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 28 Jun 2024 20:58:05 +0200 (CEST) Injection-Info: dont-email.me; posting-host="22d6777b5c707f7cb6c3ff9239a468d6"; logging-data="3651261"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Ma3Ftv0/yj7/A7SjFpxXDG5xSPE1nOac=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:Z5fmyxZm21cMfFR1yYi+3FsKs5M= In-Reply-To: Bytes: 1711 Am 28.06.24 um 09:23 schrieb Ralf Fassel: > * aotto1968 > | should be >> > | proc block {args code} { > | ... > | } >> > | "args" always collect as much as possible arguments > | { args code } first set the defined "code" from the "end" and > | all remaining arguments got to "args" > > Note that the TCL 'args' works differently: it is only 'magic' if it is > the *last* entry in the argument list. Yes, but it would indeed be useful; hence TIP 288 https://core.tcl-lang.org/tips/doc/trunk/tip/288.md (unfortunately, rejected for 9.0) Christian