fireartist

Recent Actions

• Commented on New Website and URL for HTML::FormFu
  The new site looks great! I'm so happy that people still find the code useful....
• Commented on Another reason not to use each()
  I think the issue here is that `each` expects a hash argument - and you're passing it a list. The more usual method of assinging to a hash would be: # assign a list to a hash variable my %thingies...
• Commented on Concurrency Weirdness
  The problem may be that changing the size of the array isn't thread safe, and you need some sort of lock. See this: http://doc.perl6.org/language/concurrency#Safety_Concerns...
• Commented on The Simplest Exporter?
  Looks like Exporter::Easiest would allow you to do: use Exporter::Easiest OK => qw( sub1 sub2 ); close enough?...
• Commented on Using modules that are not installed
  I think this would be equivalent to both those lines: use blib 'MODULEB';...
• Commented on Seeking: Module to plot Perl class hierarchy
  The latest dev version of Class::Sniff has a `csniff` program that'll create a graphic file with this. http://use.perl.org/~Ovid/journal/39010 http://search.cpan.org/~ovid/Class-Sniff-0.08_05/...
• Posted Lacuna Expanse conspiracy theory to fireartist

  Has Lacuna Expanse been created solely to cripple Perl developers' productivity?

  Are tiobe.com the real developers of Lacuna Expanse, in a fiendish plot to further lower perl's ranking?

  Who cares?!
  The Saben Semesne are attacking!

• Commented on Speeding Up Code
  I don't recognise that particular warning, but I do normally need to apply a/some patches from its RT queue before it'll complile - particularly on solaris - it seems to have a memory leak, reducing the effective max number of...
• Commented on Speeding Up Code
  PersistentPerl on cpan is definitely worth a look - I use it to drive a heavy Catalyst / DBDx::Class app...
• Posted FormFu - trying to make forms suck less to fireartist

  Well, google this title and it'll return almost 2 million results - so it's not an original idea, but it's worth a try. So how far along have we come this past year?

  My favourite new feature is "method name suffixes" in ="http://search.cpan.org/~cfranks/Catalyst-Controller-HTML-Form…

Comment Threads

• Pawel bbkr Pabian commented on Concurrency Weirdness

  Liz: that is expected, quote from mkfifo manpage:

  "Opening a FIFO for reading normally blocks until some other process opens the same FIFO for writing, and vice versa."

• Aaron Baugher commented on Concurrency Weirdness

  Thanks everyone for the ideas. Yes, a named pipe blocks until a process reads from it. So that part works: as soon as I read from it, that loop continues, printing the array to the filehandle, closing it, and starting over. But while it's waiting, it stops the other thread. I'll check out the stuff on thread safety and try some different arrangements. Thanks again.

• Aaron Baugher commented on Concurrency Weirdness

  I tried replacing the named pipe open with something else that would block -- reading a line from a pipe to grep without a filename -- to make sure it wasn't the named pipe itself causing the problem. Looks like it wasn't, because the for loop still starts and then stops after some lines. So I'm off to learn about thread safety!

• Aristotle commented on Another reason not to use each()

  fireartist: I’m afraid everything you said is wrong, and your entire analysis is mistaken.

  In the best case, it would be redundant with bigfoot’s own analysis, who had already identified the problem correctly in the followup section of the post.

  Here’s a thought experiment for what you’re missing: how come push @foo, $bar pushes something onto @foo?

  Why doesn’t that pass the contents of @foo to push?

  I think that must be special-cased in the parser

  You’re pretty cl…

• bigfoot commented on Another reason not to use each()

  I think you missed the point. The dereferencing was so that I could inline a hash for each. It is in fact a hash, not a list.

  my %thingies = %{{qw/a 1 b 2 c 3/}};

  That line was just to pull it out of the loop. No one would never write that.

  The problem is that Perl is recreating the hash each time through the loop...obvious after it is described, but again I assumed an optimization that does not exist in Perl (only create the hash once).