From jeff at imaginative-software.com Tue Aug 6 18:37:13 2013 From: jeff at imaginative-software.com (Thalhammer, Jeffrey) Date: Tue, 6 Aug 2013 18:37:13 -0700 Subject: [Chicago-talk] [JOB] Stratopan.com Is Hiring Message-ID: Hello Chicago- This is your chance to be part of a project that will make a big impact in the Perl world! We're looking for someone with design talent to polish the site before going into beta later this month. This is a short and sweet project with well-defined goals and deliverables. If the beta goes well, there will be an opportunity for more extensive work. You'll need some experience with Bootstrap, and good taste. Be comfortable navigating HTML template files. Go to https://alpha.stratopan.com to see what you'll be working with. Contact team at stratopan.com and we'll give you the specs. Looking forward to hearing from you! -------------- next part -------------- An HTML attachment was scrubbed... URL: From madcityzen at gmail.com Wed Aug 7 10:34:58 2013 From: madcityzen at gmail.com (Doug Bell) Date: Wed, 7 Aug 2013 12:34:58 -0500 Subject: [Chicago-talk] Meetings for August Message-ID: <2935602425710404173@unknownmsgid> With the project night change from Thursday to Wednesday, we've got a bit of an odd schedule this month: Wednesday, August 14: Workshop Planning Meeting. This replaces our usual project night, and is for anyone interested in helping to plan a one-day Perl workshop in Chicago. Thursday, August 22: Presentation. I'm throwing my hat into the ring this month. I've got quite a few presentations that are basically ready, so if anyone has a preference, let me know: 1) Building Mojolicious Apps with Angular and Bootstrap 2) Testing with Perl (Test::More, Test::Deep, Test::Differences, Test::Exception, Test::Class::Moose) 3) Basic Shell Essentials (the basics of how to use a shell to get things done) 4) Perl as a Shell Tool (Perl one-liners) 5) Working with CPAN (consuming and publishing) If there is no other preference, I'll go with number 1. Doug Bell madcityzen at gmail.com From jschueler at eloquency.com Tue Aug 13 12:06:35 2013 From: jschueler at eloquency.com (Jim Schueler) Date: Tue, 13 Aug 2013 15:06:35 -0400 (EDT) Subject: [Chicago-talk] Announcing Contextual::Return::Wrapper In-Reply-To: <2935602425710404173@unknownmsgid> References: <2935602425710404173@unknownmsgid> Message-ID: I discussed a work in progress at the last meeting. Finally got it up on CPAN http://search.cpan.org/~tqisjim/Contextual-Return-Wrapper-0.01/lib/Contextual/Return/Wrapper.pm Jim! From dcmertens.perl at gmail.com Wed Aug 21 05:11:50 2013 From: dcmertens.perl at gmail.com (David Mertens) Date: Wed, 21 Aug 2013 08:11:50 -0400 Subject: [Chicago-talk] Announcement: Alien Module and Bindings for the Tiny C Compiler Message-ID: Hello everyone! I have finally written and uploaded the first version of Alien::TinyCC and the second version of C::TinyCompiler. I am spamming all of you because either (1) it seems appropriate for the list or (2) I think that you might be interested based on personal conversations we've had. *The Tiny C Compiler* is a small, fast, nearly C99 compliant C compiler written for Linux and Windows, which can also compile object code on Mac (but cannot produce Mach-O executables or dylibs). It targets 32- and 64-bit Intel instruction sets as well as ARM architectures. The compiler is very fast, but what you get in compile-time speed you lose in non-optimized machine code. However, it's still machine code, and it offers a library that includes functionality for compiling arbitrary strings of C code at runtime! For development, see http://savannah.nongnu.org/projects/tinycc. *C::TinyCompiler* provides an interface to using that just-in-time compilation capability, as well as a framework for building reusable components in the system. If you are using one of the major platforms and have to generate code at runtime, this will probably be a better tool for you than Inline::C. If your C code is static, the one-time hit for compilation will pay for itself with the caching mechanism, and the code will execute faster, so you're better off sticking with Inline::C in that case. For development, see https://github.com/run4flat/perl-TCC. *Alien::TinyCC* installs the Tiny C Compiler to a non-invasive location which is almost certainly not in the user's path, but the module itself fiddles with $ENV{PATH} and, possibly, $ENV{LD_LIBRARY_PATH} to ensure that the compiler and its main library are available within the Perl environment that invokes the module. Note that this module does not pay any attention to a local install of tinycc, it *always* installs tcc under the distribution sharedir for Alien::TinyCC. For development, see https://github.com/run4flat/Alien-TinyCC. *New as of this morning* is the Alien module, and the modification to C::TinyCompiler to use it. Now C::TinyCompiler has a decent chance of building and operating on the most popular systems. I expect to hit a few bumps, of course, so I am writing to solicit *testing and feedback*. Please spread the word to any and all who might be interested. Also, there is plenty of room for improving C::TinyCompiler, especially fleshing out C::TinyCompiler::Perl as well as making C::TinyCompiler::Callable more efficient. I would also be happy to see modules that provide C::TinyCompiler interfaces to C libraries. Thanks! David -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan -------------- next part -------------- An HTML attachment was scrubbed... URL: From madcityzen at gmail.com Wed Aug 21 07:47:14 2013 From: madcityzen at gmail.com (Doug Bell) Date: Wed, 21 Aug 2013 09:47:14 -0500 Subject: [Chicago-talk] Modern Web Apps with Mojolicious, Angular.js, and Bootstrap - Thursday, August 22 Message-ID: Hello everyone! We've got a presentation tomorrow, Thursday, August 22. I'll be giving a talk on combining Mojolicious, Angular.js, and Twitter Bootstrap to create modern web applications with RESTful APIs and responsive UI. Our meeting will be held in our usual location, 540 W Madison, in the 9th floor conference rooms. RSVP on the Meetup page to get entrance into the building: http://www.meetup.com/ChicagoPM/events/135173492/ Pizza and beverages will be provided. The schedule will be: ? 6:30pm - Arrival and food/drink ? 7:00pm - Presentation ? 8:30pm - Other discussion Doug Bell madcityzen at gmail.com From joel.a.berger at gmail.com Wed Aug 21 10:11:38 2013 From: joel.a.berger at gmail.com (Joel Berger) Date: Wed, 21 Aug 2013 12:11:38 -0500 Subject: [Chicago-talk] Announcement: Alien Module and Bindings for the Tiny C Compiler In-Reply-To: References: Message-ID: Very cool. I have some questions which I can pose when I'm on a non mobile platform. For now you might want to consider adding the meta merge for your github repo and tracker. That way the websites correctly list them and bugs go to the right place. See most of my modules for examples if needed. Congrats! On Aug 21, 2013 7:29 AM, "David Mertens" wrote: > Hello everyone! > > I have finally written and uploaded the first version of Alien::TinyCC and > the second version of C::TinyCompiler. I am spamming all of you because > either (1) it seems appropriate for the list or (2) I think that you might > be interested based on personal conversations we've had. > > *The Tiny C Compiler* is a small, fast, nearly C99 compliant C compiler > written for Linux and Windows, which can also compile object code on Mac > (but cannot produce Mach-O executables or dylibs). It targets 32- and > 64-bit Intel instruction sets as well as ARM architectures. The compiler is > very fast, but what you get in compile-time speed you lose in non-optimized > machine code. However, it's still machine code, and it offers a library > that includes functionality for compiling arbitrary strings of C code at > runtime! For development, see http://savannah.nongnu.org/projects/tinycc. > > *C::TinyCompiler* provides an interface to using that just-in-time > compilation capability, as well as a framework for building reusable > components in the system. If you are using one of the major platforms and > have to generate code at runtime, this will probably be a better tool for > you than Inline::C. If your C code is static, the one-time hit for > compilation will pay for itself with the caching mechanism, and the code > will execute faster, so you're better off sticking with Inline::C in that > case. For development, see https://github.com/run4flat/perl-TCC. > > *Alien::TinyCC* installs the Tiny C Compiler to a non-invasive location > which is almost certainly not in the user's path, but the module itself > fiddles with $ENV{PATH} and, possibly, $ENV{LD_LIBRARY_PATH} to ensure that > the compiler and its main library are available within the Perl environment > that invokes the module. Note that this module does not pay any attention > to a local install of tinycc, it *always* installs tcc under the > distribution sharedir for Alien::TinyCC. For development, see > https://github.com/run4flat/Alien-TinyCC. > > *New as of this morning* is the Alien module, and the modification to > C::TinyCompiler to use it. Now C::TinyCompiler has a decent chance of > building and operating on the most popular systems. I expect to hit a few > bumps, of course, so I am writing to solicit *testing and feedback*. > > Please spread the word to any and all who might be interested. Also, there > is plenty of room for improving C::TinyCompiler, especially fleshing out > C::TinyCompiler::Perl as well as making C::TinyCompiler::Callable more > efficient. I would also be happy to see modules that provide > C::TinyCompiler interfaces to C libraries. > > Thanks! > David > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." -- Brian Kernighan > > _______________________________________________ > Chicago-talk mailing list > Chicago-talk at pm.org > http://mail.pm.org/mailman/listinfo/chicago-talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: