{"thread":{"id":"2218","subject":"Re: The MIT error","startedAt":"2005-10-25T13:40:16Z","lastAt":"2005-10-25T16:50:03Z","messageCount":3,"participants":["Horst von Brand","Andreas Ericsson","H. Peter Anvin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"10579","messageId":"200510251340.j9PDeGGt006248@laptop11.inf.utfsm.cl","threadId":"2218","inReplyTo":"mwelinder@gmail.com","subject":"Re: The MIT error","fromName":"Horst von Brand","fromEmail":"vonbrand@inf.utfsm.cl","sentAt":"2005-10-25T13:40:16Z","receivedAt":"2005-10-25T13:40:16Z","isPatch":false,"sender":{"key":"vonbrand@inf.utfsm.cl","avatar":"https://avatars.githubusercontent.com/u/211384?v=4"},"body":"Morten Welinder wrote:\n> After the isspace/BSD conflict I looked into what reserved symbols are\n> being used by git. Quite a few, it turns out.\n\n[...]\n\n> Just as isspace is reserved by the C implementation...\n> \n> 7.26.2 Character handling \n> \n> [#1] Function names that begin with either is or to, and a\n> lowercase letter (possibly followed by any combination of\n> digits, letters, and underscore) may be added to the\n> declarations in the header.\n\nThere go is_space(), etc as suggested by the relevant patches... in any\ncase, if you /don't/ #include , you are safe (standardwise),\naren't you? [Yes, idiots who #include that in system headers are way\nbroken, but...]\n-- \nDr. Horst H. von Brand User #22616 counter.li.org\nDepartamento de Informatica Fono: +56 32 654431\nUniversidad Tecnica Federico Santa Maria +56 32 654239\nCasilla 110-V, Valparaiso, Chile Fax: +56 32 797513\n"},{"id":"10580","messageId":"435E3892.4020002@op5.se","threadId":"2218","inReplyTo":"200510251340.j9PDeGGt006248@laptop11.inf.utfsm.cl","subject":"Re: The MIT error","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2005-10-25T13:52:18Z","receivedAt":"2005-10-25T13:52:18Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Horst von Brand wrote:\n> Morten Welinder wrote:\n> \n>>After the isspace/BSD conflict I looked into what reserved symbols are\n>>being used by git. Quite a few, it turns out.\n> \n> \n> [...]\n> \n> \n>>Just as isspace is reserved by the C implementation...\n>>\n>> 7.26.2 Character handling \n>>\n>> [#1] Function names that begin with either is or to, and a\n>> lowercase letter (possibly followed by any combination of\n>> digits, letters, and underscore) may be added to the\n>> declarations in the header.\n> \n> \n> There go is_space(), etc as suggested by the relevant patches...\n\n\nNo they don't. \"begin with either is or to and a lowercase letter\", \nmeaning (is|to)[a-z].*, just as Morten wrote. is_.* doesn't fall into \nthis category. The underscore exemption is so that users can write their \nown is_file(), is_whatever() str_replace() and such. Some thought has \ngone into the standard.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"10588","messageId":"435E623B.20303@zytor.com","threadId":"2218","inReplyTo":"435E3892.4020002@op5.se","subject":"Re: The MIT error","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-10-25T16:50:03Z","receivedAt":"2005-10-25T16:50:03Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Andreas Ericsson wrote:\n> \n> No they don't. \"begin with either is or to and a lowercase letter\", \n> meaning (is|to)[a-z].*, just as Morten wrote. is_.* doesn't fall into \n> this category. The underscore exemption is so that users can write their \n> own is_file(), is_whatever() str_replace() and such. Some thought has \n> gone into the standard.\n> \n\nAlso, note that we don't include , and the reasons to stay out \nof its namespace are:\n\na. potential for confusion (different semantics), and\nb. broken system headers.\n\n\t-hpa\n"}]}