Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Wed, 5 Aug 2009 02:39:57 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n750duVv028989 for ; Wed, 5 Aug 2009 02:39:56 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n750YQEX028168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Aug 2009 02:34:26 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n74M1QT9007784; Wed, 5 Aug 2009 02:34:24 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 284232 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 5 Aug 2009 02:34:24 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n750YNfZ019483 for ; Wed, 5 Aug 2009 02:34:23 +0200 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.247]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n750YHon004507 for ; Wed, 5 Aug 2009 02:34:21 +0200 Received: by rv-out-0708.google.com with SMTP id c5so1142662rvf.10 for ; Tue, 04 Aug 2009 17:34:18 -0700 (PDT) Received: by 10.141.37.8 with SMTP id p8mr5768480rvj.156.1249432458541; Tue, 04 Aug 2009 17:34:18 -0700 (PDT) Received: from ?129.127.15.244? ([129.127.15.244]) by mx.google.com with ESMTPS id k37sm4223120rvb.2.2009.08.04.17.34.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 04 Aug 2009 17:34:17 -0700 (PDT) Content-Type: multipart/signed; boundary=Apple-Mail-2-542313823; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v935.3) References: <4A781594.8060202@elzevir.fr> <4A78A9FE.5020309@morningstar2.co.uk> X-Mailer: Apple Mail (2.935.3) X-Spam-Whitelist: Message-ID: Date: Wed, 5 Aug 2009 10:04:13 +0930 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: using expl3 for latex2e packages To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <4A78A9FE.5020309@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 05 Aug 2009 00:39:57.0541 (UTC) FILETIME=[41ECF950:01CA1565] Status: R X-Status: X-Keywords: X-UID: 5814 --Apple-Mail-2-542313823 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Hi Manuel, Just a short note to back up what Joseph just said. On 05/08/2009, at 7:07 AM, Joseph Wright wrote: > For the record here, the idea is that expl3 is stable. By all means, in our so-far limited applications of the codebase, it seems ready to use to us. One of the reasons that we've been able to change things at all is that no-one is relying on the code for anything. Now that people are starting to use it we have a much greater responsibility in not breaking anything. I do still expect there will be some evolution with the feedback of more users such as yourself, but this should mostly be in areas of growth (i.e., where things are missing) rather than change. As far as I'm concerned, it's now or never for the expl3 code (some might even say it's too late). I think we're at a stage where we can state: we've iterated some ideas and this seems the best we can achieve; if you use it now we will support backwards compatibility to the best of our ability. I hope the rest of the team agrees with this, more or less. Will P.S. Joseph, I can't help noticing your use of \cs_new_nopar:Nn. I know that without an argument this usage is (in TeX terms) more "correct". But, unless I was drastically mistaken, the assumption we made when naming these functions was that it didn't really matter to have some spurious \long's and we really wanted people to use \cs_new:Nn in all cases except when they *specifically* wanted to restrict \par. (Since the \long case is more general and more frequent. Restricting \par in the input is better achieved when defining the user commands than the underlying commands beneath them.) Unfortunately, there are lots of cases in source3 where this convention is not followed, but only because the translation was performed mechanically. What do you think about the whole thing? --Apple-Mail-2-542313823 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGITCCAtow ggJDoAMCAQICECN4qE5kBXLk2f/jVDfSZPwwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDEyOTA1NDkxNVoXDTEwMDEyOTA1NDkx NVowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0GCSqGSIb3DQEJARYQd3Nw cjgxQGdtYWlsLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL0BeSiAbKuqxeRN p2qn/m8ZL+xawr/WXyPgEF0FipWgRe9l3sMXcFHokcUu0xOc97R7xkUsGcQ8EyybGHuWey6x7X1Y xJZXnoAxqcaG+eREytoYGMIKs6BhEEogLVb2ERw3lQNVnOzanSFeGo8suMAN4zzCtqAjJiA1ph7h 1pksTgECYK5EiIZbFsB6zSDa8crNk404z1CfIA6YO8ezvjbDda+D0r8NU2tq9WS9F5IaG+bW71Ya JegEcSZ+WF6Z+fs2MUMCLLu8n50Er0nuy4dxOmkdMRNfbeaM39dsEwjAAgcQnvPNmlJ215nZWQRH 49YowtSBOYUYq0ZylWRE6x8CAwEAAaMtMCswGwYDVR0RBBQwEoEQd3NwcjgxQGdtYWlsLmNvbTAM BgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBABaRP8+PDYpKIRGlFgjs1HvMmJnqu4reSqp+ ulv0zJZIjIbX/sLbIsnecl9nycHfhubPdc+hDfpCqNZ2+NGQHwwoyuDl7KOdTY0BDPp3eJLio7ob EYEr0H8rFwqfx2LWJ0G6nMhNEjLvs7sFKyriSpk++TWJnnsf86xai5m0tlOwMIIDPzCCAqigAwIB AgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UE CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUu Y29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNV BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7 TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/ cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRA HmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYy aHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0P BAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG 9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8 /a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQ Gls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYwYjELMAkGA1UEBhMCWkExJTAj BgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAjeKhOZAVy5Nn/41Q30mT8MAkGBSsOAwIaBQCgggFv MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA5MDgwNTAwMzQxM1ow IwYJKoZIhvcNAQkEMRYEFG5Y7gpn7wndW6IQFsfevWwISGc3MIGFBgkrBgEEAYI3EAQxeDB2MGIx CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQI3ioTmQFcuTZ/+NUN9Jk /DCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz dWluZyBDQQIQI3ioTmQFcuTZ/+NUN9Jk/DANBgkqhkiG9w0BAQEFAASCAQADJR2n/S3yARGy5Pc0 eaMIsE12HOiPjnFW2q9jJ4TQrEmmEQD0e3SFFzCkZO3U1U/XNmlgQ2fPtI/8I2ljkLl2NEMXjCx8 4ctBMiiORfHyfNvrwvlHXzkNwApU1AEPmmd2ES1vZ2w0k9eEhaVcUxOOOSSqxz+hTBLphqEuH+tu kitL031J6iLFJRV2EcwZuhr+//UXfWoDDSgX24GnwrnRnbdXnhSWN3eV+BnERPWicy1JcvNcPDDC 5Mm+Gn899f/dHTP9dIxYqQVCbyYpm9lf+7B8/Uhau979hT3uD+hqJuJ0/T0PdCwak2yP/Vb/rh2y 4vy3VnBq/HkG4LMK7y27AAAAAAAA --Apple-Mail-2-542313823--