X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["450" "Fri" "14" "January" "1994" "23:37:51" "+0000" "Chris Rowley | OU - UK [R01/Maths]" "C.A.Rowley@open.ac.uk" "<199401151233.AA05486@mail.cs.tu-berlin.de>" "15" "Re: parameter stack in 2e" "^Date:" nil nil "1" "1994011423:37:51" "parameter stack in 2e" (number " " mark " Chris Rowley | OU Jan 14 15/450 " thread-indent "\"Re: parameter stack in 2e\"\n") nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA20463; Sat, 15 Jan 94 13:37:05 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA29797; Sat, 15 Jan 94 13:35:34 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA05486 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Sat, 15 Jan 1994 13:33:53 +0100 Message-Id: <199401151233.AA05486@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 9881; Sat, 15 Jan 94 00:39:21 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 9880; Sat, 15 Jan 1994 00:39:21 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 7469; Sat, 15 Jan 1994 00:39:08 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Fri, 14 Jan 1994 23:37:51 +0000 From: "Chris Rowley | OU - UK [R01/Maths]" Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: parameter stack in 2e Status: R X-Status: X-Keywords: X-UID: 1280 Sebastian writes: > consider the log file that follows; class is article, which includes > package texps, which includes package graphics, which includes > package calc. result, a bomb due to too much nesting. > > is my setup unreasonable, or should I *not* expect this from my TeX or > or my 2e? is this TeX, or 2e doing something clever It is 2e being outstandingly clever, and eating up parameter stack in the process. It will be fixed. chris