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 ]

+ -

  Comment: Thanks (Score 1) on 2010.08.20 14:55

by markjugg on 2010.08.20 14:55 (#72333)
Attached to: New WWW::Salesforce release details

Thanks, I appreciate the new release.

Read More 1 comments
Comments: 1
+ -

  Comment: how do you like it? (Score 1) on 2009.11.17 10:25

by markjugg on 2009.11.17 10:25 (#71152)
Attached to: Vim: Automatically opening POD as a PDF
Interesting idea. How do you like using it in practice?
Read More 2 comments
Comments: 2
+ -

  Comment: me too (Score 1) on 2009.11.17 10:22

by markjugg on 2009.11.17 10:22 (#71151)
Attached to: Why no plan for nested TAP?
I also strongly support your proposed patch. For me, it could mean the difference between using and enjoying subtests, and not adopting them.
Read More 14 comments
Comments: 14
+ -

  Comment: the summary line: before or after the subtest? (Score 1) on 2009.11.02 11:18

by markjugg on 2009.11.02 11:18 (#71032)
Attached to: Using subtests

I tried using this today and noticed another detail: The subtest name is printed *after* the sub-test output. I expected that it would be printed *before* the output, as it appears in the test.

I don't know if this change is possible with the TAP structure or not.

Read More 3 comments
Comments: 3
+ -

  Comment: useful example (Score 1) on 2009.10.26 15:36

by markjugg on 2009.10.26 15:36 (#70976)
Attached to: Using subtests

This was a useful example, Ovid.

I agree being able to skip declaring a plan inside of a subtest would be a nice feature.

Read More 3 comments
Comments: 3
+ -

  Comment: distribute the full stack (Score 1) on 2009.10.21 12:40

by markjugg on 2009.10.21 12:40 (#70935)
Attached to: Downgrading Moose

My idea for a solution for CPAN to automate distributing the full stack of dependencies of modules. So in addition to a "download" link for a module, there would be a "download with all dependencies" option.

Some related pieces:

- Authors should be stricter about which versions of modules they require, and favor the practice of depending on versions they have tested against rather than defaulting to "whatever the newest version of the depending is"... which may not even be released yet!

- For modules that provide Pure Perl and XS alternatives, there should be a standard way for automated tools to build the Pure Perl version.

- Like Ubuntu or Debian, we could make use of a "build farm" that would compile the XS bits on various platforms.

In your case, it would mean that when selected an old version of Moose, you would have the option to download the old version with all dependencies that the old version depended on, instead of getting the old version...and then getting all the newest dependencies.

It's my dream.

Read More 9 comments
Comments: 9
+ -

  Comment: Thanks (Score 1) on 2009.06.07 20:59

Looks like a useful breakthrough. Bookmarked. Thanks! Mark
Read More 3 comments
Comments: 3
+ -

  Comment: Re:Movable Type (Score 1) on 2009.05.29 12:29

by markjugg on 2009.05.29 12:29 (#68849)
Attached to: Leave use.perl?

If someone makes a case that CGI::Explorer would be a good replacement for some they do internally now, I think it would be considered.

Read More 19 comments
Comments: 19
+ -

  Comment: Movable Type (Score 1) on 2009.05.19 13:10

by markjugg on 2009.05.19 13:10 (#68657)
Attached to: Leave use.perl?

I've been happy using (perl-based) Movable Type on a shared hosting account. Using a perl-based blogging platform is one more way to support the community. (And there is talk in the MT community of refactoring it to use CGI::Application and other CPAN modules).

It runs multiple blogs out of the box, so you can easily run your technical blog and personal blog in one place, as I do:

http://mark.stosberg.com/blog
http://mark.stosberg.com/bike

My "Perl" category is subscribed to by PerlSphere.

I also prefer the philosophy of a decentralized grassroots network of blogs, rather than giving centralized control to some third-party organization.

Read More 19 comments
Comments: 19
+ -

  Comment: great tips (Score 1) on 2009.04.27 9:34

by markjugg on 2009.04.27 9:34 (#68324)
Attached to: Tips For Converting Base Classes Into Roles

Great tips! Thanks. I'm getting sold on roles-centric programming.

It would be great to have a index page somewhere of all your posts about roles.

Read More 3 comments
Comments: 3
+ -

  Comment: sold (Score 1) on 2009.04.10 10:06

by markjugg on 2009.04.10 10:06 (#68070)
Attached to: Before and After Graphs (Role Application)
Ovid, I regularly read and enjoy your blog posts. I think your latest series on roles has sold me on moving more in that direction in my own work. I agree it seems like a cleaner, clearer organizational model than focusing on inheritance.
Read More 2 comments
Comments: 2
+ -

  Comment: bug: my $DIR = 'lib/'; (Score 1) on 2009.04.01 13:39

by markjugg on 2009.04.01 13:39 (#67987)
Attached to: use_ok is not ok.

There's a bug here that I didn't spot until I tried to run it:

  my $DIR => 'lib/';

I think you mean "=" there, not =>

Read More 10 comments
Comments: 10
+ -

  Comment: a good case for darcs (Score 1) on 2009.03.26 11:56

by markjugg on 2009.03.26 11:56 (#67921)
Attached to: The "Joy" of Tight Deadlines
I'm a project now with a similar structure, and we just launched "phase 1" today.

darcs managed the complications of this workflow very elegantly. We actually only created one feature branch off of the trunk. They we created one ticket tracking number for each launch.

To launch phase one, a developer took a local co py of the feature branch, removed all the patches that were for the second phase, by referencing the phase2 ticket number (darcs oblit -p phase2), and then pushed the result to the trunk. Of course, there were some details and edge cases, but overall darcs handled everything rather well.

Read More 2 comments
Comments: 2
+ -

  Journal: Moving my Perl blogging from use.perl.org on 2008.12.31 16:28

Journal by markjugg on 2008.12.31 16:28
User Journal

Joining several others, I'm moving my Perl blogging off of use.perl.org. My personal Perl blog posts will be here.

I sometimes write about Perl on my company blog here.

On my own site, I'll be able to see my own traffic stats, control the SEO, and provide a unique design. I think having a plurality of blogs promoting and discussing Perl is a good thing.

Read More 0 comments

+ -

  Comment: trash can ++ (Score 1) on 2008.12.31 14:00

by markjugg on 2008.12.31 14:00 (#66685)
Attached to: alias rm "rm -i" (slips vs mistakes)

The trash can concept is such a useful idea, adopted by all the major desktop operating systems.

It perhaps says something about geek culture that it is not yet built into major command line interfaces. I wish it was.

Read More 11 comments
Comments: 11