RE: Inline::C Cookbook addition
[email protected] ("Konovalov, Vadim") Sun, 5 Feb 2017 18:44:04 +0000
| Newsgroups | perl.inline |
|---|---|
| Message-ID | <[email protected]> |
--_000_8FC9F990A991F24AA0166C36379560B98019BF8CMX106CL01corpem_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Too much attention to unrelated details such as SvPV_nolen With this amount of explanations - I would throw away closely unrelated tex= t but in return insert there another colorful examples, which in turn uncov= er something useful. And even I would remove "use warnings;" line - inserting it here there and = everywhere is just eating useful screen space of information. The shorter the better... Consider that you've already convinced all around people to actually insert= this "use warnings;" and no more need to convince people even more. Other than that - nice wording, nice effort, thank you for that, you're mak= ing world better :):) From: Ron Grunwald via inline [mailto:[email protected]] Sent: Sunday, February 05, 2017 5:38 PM To: [email protected] Subject: Re: Inline::C Cookbook addition Hi all, Just providing an update to this thread. I did end up submitting an updated= "Cookbook.swim" as a pull request with the help of several contributors. A= few days ago, Ingy was kind enough to merge the change with the Inline::C = master branch. The new recipe is titled "Direct Access to Perl variables" and is placed at= the end of the section "Meat & Potatoes". Thank you to everyone who assisted me. Cheers, Ron. On 21 Dec 2016, at 7:16 am, [email protected]<mailto:sisyphus1@optu= snet.com.au> wrote: From: Ron Grunwald Sent: Wednesday, December 21, 2016 9:33 AM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: Inline::C Cookbook addition This mailing list is very quiet these days and I think your request will pr= obably fall "through the cracks" unless you submit it as a github "Issue" o= r a github pull request. For completeness, I did write up the recipe and submitted it as an issue on= github about 3 days ago, https://github.com/ingydotnet/inline-c-pm/issues/56 There havn't been any comments made so far, so I'm not sure if its being co= nsidered for the C Cookbook. Also, it looks like no updates were made to Inline::C for the last two year= s. Cheers, Ron Hi Ron, Yes, I don't know when your request will be acted upon. But it's now in a place where it won't get lost - and whenever someone deci= des to update Inline::C they should see that request and give it the consid= eration it deserves. Cheers, Rob --_000_8FC9F990A991F24AA0166C36379560B98019BF8CMX106CL01corpem_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Avenir-Book; panose-1:0 0 0 0 0 0 0 0 0 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p.MsoAcetate, li.MsoAcetate, div.MsoAcetate {mso-style-priority:99; mso-style-link:"Balloon Text Char"; margin:0in; margin-bottom:.0001pt; font-size:8.0pt; font-family:"Tahoma","sans-serif";} span.BalloonTextChar {mso-style-name:"Balloon Text Char"; mso-style-priority:99; mso-style-link:"Balloon Text"; font-family:"Tahoma","sans-serif";} span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:56.7pt 42.5pt 56.7pt 85.05pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Too much attention to unr= elated details such as SvPV_nolen <o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">With this amount of expla= nations – I would throw away closely unrelated text but in return ins= ert there another colorful examples, which in turn uncover something useful.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">And even I would remove &= #8220;use warnings;” line – inserting it here there and everywh= ere is just eating useful screen space of information.<o:p></o:p></span></p= > <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">The shorter the better= 230;<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Consider that you’v= e already convinced all around people to actually insert this “use wa= rnings;” and no more need to convince people even more.<o:p></o:p></s= pan></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D">Other than that – n= ice wording, nice effort, thank you for that, you’re making world bet= ter </span><span style=3D"font-size:11.0pt;font-family:Wingdings;color:#1F497D"= >JJ</span><span style=3D"font-size:11.0pt;font-family:"Calibri",&= quot;sans-serif";color:#1F497D"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri","sans-serif";color:#1F497D"><o:p> </o:p></span><= /p> <div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"= ;Tahoma","sans-serif"">From:</span></b><span style=3D"font-s= ize:10.0pt;font-family:"Tahoma","sans-serif""> Ron Grun= wald via inline [mailto:[email protected]] <br> <b>Sent:</b> Sunday, February 05, 2017 5:38 PM<br> <b>To:</b> [email protected]<br> <b>Subject:</b> Re: Inline::C Cookbook addition<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Hi all,<o:p></o:p></p> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">Just providing an update to this thread. I did end u= p submitting an updated "Cookbook.swim" as a pull request with th= e help of several contributors. A few days ago, Ingy was kind enough to mer= ge the change with the Inline::C master branch.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal">The new recipe is titled "<span style=3D"font-f= amily:"Avenir-Book","serif"">Direct Access to Perl vari= ables" and is placed at the end of the section "Meat & P= otatoes".</span><o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Avenir-Book",&= quot;serif"">Thank you to everyone who assisted me.</span><o:p></o:p><= /p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Avenir-Book",&= quot;serif"">Cheers,</span><o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f= amily:"Avenir-Book","serif"">Ron.</span><o:p></o:p></p> <div> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <div> <p class=3D"MsoNormal">On 21 Dec 2016, at 7:16 am, <a href=3D"mailto:sisyph= [email protected]"> [email protected]</a> wrote:<o:p></o:p></p> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal">From: Ron Grunwald<br> Sent: Wednesday, December 21, 2016 9:33 AM<br> To: <a href=3D"mailto:[email protected]">[email protected]<= /a><br> Cc: <a href=3D"mailto:[email protected]">[email protected]</a><br> Subject: Re: Inline::C Cookbook addition<br> <br> <br> <o:p></o:p></p> <blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt"> <p class=3D"MsoNormal">This mailing list is very quiet these days and I thi= nk your request will probably fall "through the cracks" unless yo= u submit it as a github "Issue" or a github pull request.<o:p></o= :p></p> </blockquote> <p class=3D"MsoNormal"><br> For completeness, I did write up the recipe and submitted it as an issue on= github about 3 days ago,<br> <br> <a href=3D"https://github.com/ingydotnet/inline-c-pm/issues/56">https://git= hub.com/ingydotnet/inline-c-pm/issues/56</a><br> <br> There havn't been any comments made so far, so I'm not sure if its being co= nsidered for the C Cookbook.<br> Also, it looks like no updates were made to Inline::C for the last two year= s.<br> <br> Cheers,<br> Ron<o:p></o:p></p> <p class=3D"MsoNormal"><br> Hi Ron,<br> <br> Yes, I don't know when your request will be acted upon.<br> <br> But it's now in a place where it won't get lost - and whenever someone deci= des to update Inline::C they should see that request and give it the consid= eration it deserves.<br> <br> Cheers,<br> Rob <o:p></o:p></p> </div> </blockquote> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </div> </body> </html> --_000_8FC9F990A991F24AA0166C36379560B98019BF8CMX106CL01corpem_--