Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

kid51 (5328)

kid51
  (email not shown publicly)
http://thenceforward.net/perl/
+ -

  YAPC::NA::2010 Schedule Out; Call for 2011 Venue on 2010.04.29 20:23 kid51

Submitted by kid51 on 2010.04.29 20:23
yapc
In case you haven't heard ...

The schedule for presentations at YAPC::NA::2010 in Columbus Ohio has been announced.

And the call for a venue for YAPC::NA::2011 is also out now.
Read More 0 comments

+ -

  Comment: Re: Help needed on a new 5.10 warning (Score 1) on 2009.09.16 22:06

by kid51 on 2009.09.16 22:06 (#70607)
Attached to: Help needed on a new 5.10 warning
All I can offer is that during some recent attempts to refactor ExtUtils::ParseXS, I encountered this warning when attempting to make that module work under 'use strict'. IIRC, I got it in a part of the code that was using the "deferred regex evaluation" feature -- ??{ $some_variable } -- inside of itself.

$bal = qr[(?:(?>[^()]+)|\((??{ $bal })\))*]; # ()-balanced

$cast = qr[(?:\(\s*SV\s*\*\s*\)\s*)?]; # Optional (SV*) cast

$size = qr[,\s* (??{ $bal }) ]x; # Third arg (to setpvn)

Again, IIRC, my temporary workaround was to declare $bal as 'our' rather than 'my'. But since my work on this module has stalled, I can't offer any better insight. Note that 'perldoc perldiag' hints at this being a closure-related problem ... but I didn't encounter it in a closure-related situation at all.

Thank you very much.

kid51

Read More 7 comments
Comments: 7
+ -

  Comment: Re: Windows Perl as a first class citizen (Score 1) on 2009.08.17 15:18

A very good summary of the issues.
Read More 22 comments
Comments: 22
+ -

  Comment: Re:Is the phalanx project dead? (Score 1) on 2009.07.26 21:06

by kid51 on 2009.07.26 21:06 (#69665)
Attached to: Corehackers Project: Thoughts on Process

I live out in the boondocks, with the nearest PM group being Berlin, a full 300km away from me.

Then make it a point to include something like the German Perl Workshop in your schedule. (I'm assuming that's Berlin, Germany, rather than, say, Berlin, New Hampshire.)

For the other, I'm not exactly a people person, ...

... which describes most geeks. And which also explains why F2F opportunities ranging from local Perlmongers meetings to hackathons to workshops to YAPCs play such an important role in our community.

Thus I was hoping that there was actually some kind of online organization associated with that, especially since refactoring code is actually one of my favourite activities.

Well, if the Corehackers Project actually gets off the ground, that will fit the bill.

But note that I learned about both the Phalanx Project and the Corehackers Project not online but in face-to-face encounters with other Perl programmers. Even if 90% of the actual work of each such project was/will be conducted by hackers working alone in their homes, the energy of such projects is crucially dependent on periodic F2F contact with your peers.

Read More 11 comments
Comments: 11
+ -

  Comment: Re:Is the phalanx project dead? (Score 1) on 2009.07.26 17:21

by kid51 on 2009.07.26 17:21 (#69659)
Attached to: Corehackers Project: Thoughts on Process
...went to check out their irc channel and it's not even in use.

I never knew we had an IRC channel! Our New York group -- which was probably the most active grouplet -- never used it.

Of course, there is absolutely nothing preventing you from embarking on the type of software improvement we were aiming for in the Phalanx project.

In the past few years, what I have done myself and have recommended others do as well is to identify CPAN distributions that look like they're not being actively maintained, contact the distro's current maintainer, and see if you can be designated as a co-maintainer. For some hints on how that works, see this talk I gave at YAPC::NA::2006 in Chicago. If you do that, I can give you pointers on how to proceed.

Read More 11 comments
Comments: 11
+ -

  Comment: But that was the point of the Phalanx project (Score 1) on 2009.07.25 22:19

by kid51 on 2009.07.25 22:19 (#69637)
Attached to: Corehackers Project: Thoughts on Process
"...without adding any features. It's hardly surprising that the author was reluctant to incorporate the changes."

But providing new features was not the point of the Phalanx Project. The point was to make the existing code better, thereby laying the basis for the authors to better add new features in the future. And that was what the module authors signed off on before we began our work.

The lesson I draw from that is that there has to be real buy-in on the part of the owners of code. That means that we should make sure the Perl 5 Porters are really on board with the Corehackers Project.

kid51

Read More 11 comments
Comments: 11
+ -

  Journal: Corehackers Project: Thoughts on Process on 2009.07.25 13:28

Journal by kid51 on 2009.07.25 13:28
User Journal
So I'm sitting in a conference hall at YAPC on either the second or third day of the conference. A veteran member of the Perl community makes a presentation in one of the short time slots about a new project in which people can help improve Perl and its ecosystem. The presenter defines a body of existing code which would benefit from study by fresh eyeballs. Such study would lead to refactoring and improvements in testing and documentation, making the c
Read More 11 comments
Comments: 11
+ -

  Comment: Re: What Parrot Shares with OpenBSD (Score 1) on 2009.07.17 19:51

by kid51 on 2009.07.17 19:51 (#69528)
Attached to: What Perl can learn from OpenBSD
Michael,

Thanks for that link. Word to whoever clicks on it: While the video quality is poor during the first 30 seconds, it becomes tolerable thereafter.

While I've read a lot about the Perl 5 release process in the past two weeks, I have no personal familiarity with it. I can, however, make some comparisons with the Parrot project.

Like OpenBSD, Parrot believes in releasing on pre-announced dates, though Parrot works on a monthly cycle rather than OpenBSD's 6-month cycle.

While we don't submit people who break trunk to the same sort of mockery that Theo describes for OpenBSD, people who do so are expected to clean up the problem quickly.

OpenBSD locks its code tree at a point a few weeks before the release data, then everyone goes into heavy testing mode. Parrot doesn't have a formal lock period per se, but we do expect people to stop making any significant commits three to four days before a release (i.e., today). And part of the reason we don't have a formal lock period is that the results we get from our Smolder reports -- many reports per day on our main OSes -- enable us to spot regressions and correct them quickly.

Thank you very much.

Read More 5 comments
Comments: 5
+ -

  Comment: But Debian and Ubuntu are harder! (Score 1) on 2009.06.13 11:43

by kid51 on 2009.06.13 11:43 (#69064)
Attached to: Apple Cats
Because Debian and Ubuntu emphasize the names of their distributions -- and because I never saw Toy Story -- I can never remember which version of Debian I have on my server and which version of Ubuntu I'm using at $job.
Read More 4 comments
Comments: 4
+ -

  Comment: Welcome to the club ... (Score 1) on 2009.05.25 22:09

... of maintainers of DCONWAY modules.
Read More 2 comments
Comments: 2
+ -

  Comment: Need to update win32.perl.org wiki with this news (Score 1) on 2009.05.01 15:34

The Strawberry Perl home page has a link in its upper-left corner taking me to this page:

http://win32.perl.org/wiki/index.php?title=Main_Page

This page was last modified 04:13, 23 October 2008.

It should be updated to contain the news of this recent Strawberry Perl release.

Read More 4 comments
Comments: 4
+ -

  Comment: Re: Leaving the Parrot nest (Score 1) on 2009.01.14 22:38

by kid51 on 2009.01.14 22:38 (#66844)
Attached to: Leaving the Parrot nest
Patrick:

Thank you for this thorough and temperate summation of the issues. I don't follow Rakudo or Perl 6 that closely; I barely have tuits to follow Parrot. So I don't have much to say one way or the other about how Rakudo's infrastructure should evolve.

I just wish we had had a blog post like this concerning Parrot's infrastructure before all these changes started happening.

Thank you very much.

Read More 9 comments
Comments: 9
+ -

  Journal: Seek better response to "How Is Perl 6 Doing?" on 2009.01.04 22:23

Journal by kid51 on 2009.01.04 22:23
User Journal
I often attend other (non-Perl) user groups in New York City -- mostly Linux and BSD groups. From time to time, when I identify myself as a Perl programmer, I am asked -- or, should I say, I am taunted with -- the question, "How is Perl 6 coming along?"

Now, up until two years ago, I simply ignored that question, because I had my hands full learning to become a good Perl 5 programmer and had no time/tuits to follow anything related to Perl 6.

Read More 7 comments
Comments: 7
+ -

  ANNOUNCE Parrot 0.7.0 on 2008.08.19 22:20 kid51

Submitted by kid51 on 2008.08.19 22:20
Parrot
Parrot release manager Bob Rogers wrote today:

On behalf of the Parrot team, I'm proud to announce Parrot 0.7.0 "Severe Macaw." Parrot is a virtual machine aimed at running all dynamic languages.

Parrot 0.7.0 is available via CPAN (soon), or follow the download instructions at here. For those who would like to develop on Parrot, or help develop Parrot itself, we recommend using Subversion on the source code repository to get the latest and best Parrot code.

Parrot 0.7.0 Highlights:
  • The new concurrency implementation makes its debut in 0.7.0.
  • Rakudo (Perl 6) now supports class attributes and multiple dispatch, plus some metaclass support, among others.

Parrot 0.7.0 News:

  • Specification
    • PDD27: add multisub lookup
  • Implementation
    • new concurrency implementation (see PDD25)
    • Exception PMC now captures a return continuation
    • improved PMC encapsulation (Iterator, Key, Pair)
  • Languages
    • Cardinal (Ruby):
      • class variables
      • parsing improvements
      • minor additions to class builtins
      • add support for block parameters to functions
    • Lua:
      • various language fixes
      • refactor all libraries (namespace, method registration)
      • add a OpenGL binding (still incomplete)
      • lost user back trace (see ppd25 & pushaction)
    • Pipp (PHP):
      • add support for while- and for-loops
      • add support for increment and decrement
      • designate PHP 5.3 as the reference implementation
      • improve support for string literals
    • Pugs (Perl 6):
      • removed due to bit rot
    • Rakudo (Perl 6):
      • now over 2200 passing spectests
      • updated the Rakudo roadmap
      • Perl 6 multi dispatch
      • dispatch with slurpies
      • class attributes ("my $.x")
      • anonymous classes
      • OO and metaclass improvements (.WHAT, .WHICH, .WHENCE)
      • additional builtin methods and subs
      • improved make test targets and harness
    • Tcl:
      • implement [lreverse], [lsort -command]
      • allow [incr] to autovivify
      • update tclsh spec target to 8.5.3
      • fix bug in TclDict PMC, allowing ~200 more [dict] spec tests to pass
      • update 'make spectest' fudging, using TODO instead of SKIP if possible
  • Compilers
    • PCT:
      • :scope('register') for PAST::Var nodes
      • allow invocant specification in attribute scope PAST::Var nodes
      • correct ordering of sub generation from POST
      • add 'loadinit' attribute to PAST::Block for block initialization
    • PIRC:
      • PIR registers now use the vanilla register allocator
      • all PASM output now uses PASM registers
      • all .locals and $registers are mapped
      • clean-up of grammar, back-end and documentation
      • implemented constant folding
      • implemented instruction selection
  • Configuration
    • tests now clean up after themselves
    • improved parallel test support
    • ports/cygwin added
    • Darwin problems fixed
  • Tools
    • parrot_debugger renamed from pdb, numerous tweaks
  • Miscellaneous
    • IMCC cleanups
    • :vtable implies self in PIR
    • modest core speed improvements
    • Cygwin support improved
    • "say" now an opcode (was dispatched to a method; see Deprecations)
  • Deprecations
    • ".pragma n_operators" is deprecated
    • old PASM register syntax (without "$") is deprecated
    • bare (unquoted) method names are deprecated
    • "#line" will be replaced with ".line"
    • ".HLL_map" syntax will change
    • ".loadlib" is now separate from ".HLL"
    • mmdvtregister and mmdvtablefind opcodes are deprecated
    • removed getfd, getclass opcodes
    • removed IMCC syntax that treated some methods as builtins
    • removed numeric get_attr and set_attr vtable entries

Many thanks to all our contributors for making this possible, and our sponsors for supporting this project. Our next scheduled release is 16 Sep 2008.

Enjoy!

— Bob Rogers

Read More 0 comments