CTAN Comprehensive TeX Archive Network

cam.ctan.org up­load: l3k­er­nel

Date: Au­gust 13, 2011 3:13:49 PM CEST
while i was out shop­ping, the dae­mon told me: > The fol­low­ing in­for­ma­tion was pro­vided by the pack­age's con­trib­u­tor. > > Name of con­tri­bu­tion: l3k­er­nel > Author's name: The LaTeX3 Project > Author's email: la­tex-team at la­tex-project.org > Pack­age ver­sion: 2564 > Lo­ca­tion on CTAN: macros/la­tex/con­trib/l3k­er­nel/ > Sum­mary de­scrip­tion: LaTeX3 pro­gram­ming con­ven­tions > Li­cense type: lppl > > An­nounce­ment text given by the pack­age's con­trib­u­tor: > ---------------------------------------------------------------------- > Snap­shot of SVN 2564 > -------------------- > > This is a main­te­nance re­lease. It in­cludes a bug fix for the > def­i­ni­tion of \Ex­plSyn­taxNamesOff. A num­ber of is­sues in l3tl have > been ad­dressed: > - \tl_re­verse:n now re­tains spaces in the in­put to­ken list. > - The be­haviour of \tl_length:n and \tl_if_sin­gle:n(TF) > with re­spect to spaces in in­put is now clearly de­fined. > - New ex­per­i­men­tal func­tions added to com­ple­ment > \tl_re­verse:n and \tl_length:n which work on a to­ken > (see the doc­u­men­ta­tion for full de­tails). > - New ex­per­i­men­tal ap­proach to con­vert­ing the case of > to­ken lists in an ex­pand­able man­ner. > - \tl_head:n and \tl_tail:n have de­fined be­haviour for > empty ar­gu­ments. thanks for the up­load; i have in­stalled the new ver­sion and up­dated the cat­a­logue repos­i­tory. > Users may view the pack­age cat­a­logue en­try at > http://www.tex.ac.uk/tex-archive/help/Cat­a­logue/en­tries/l3k­er­nel.html > or they may browse the pack­age di­rec­tory at > http://www.tex.ac.uk/tex-archive/macros/la­tex/con­trib/l3k­er­nel/ The cat­a­logue en­try will change (some­what) overnight tonight. Robin Fair­bairns For the CTAN team

l3k­er­nel – 3 pro­gram­ming con­ven­tions

The l3k­er­nel bun­dle pro­vides an im­ple­men­ta­tion of the 3 pro­gram­mers’ in­ter­face, as a set of pack­ages that run un­der . The in­ter­face pro­vides the foun­da­tion on which the 3 ker­nel and other fu­ture code are built: it is an API for pro­gram­mers. The pack­ages are set up so that the 3 con­ven­tions can be used with reg­u­lar pack­ages.

Ver­sion 2018-10-19
Copy­right1990–2018 The Project
Main­tainerThe Team



Guest Book Sitemap Contact Contact Author