point people at #perl-help first to maximize chance of actually being helped

[wchristian]

Most of the time conversations in #win32 look like this:

(mib_4ql3ih) Is the information if a module is thread-safe available somewhere? I see Term::ReadKey is causing 30% of the crashes. So 2.33 - is it threadsafe? How to find out?
(Mithaldu) mib_4ql3ih: honestly, i'm not sure about that myself. maybe better asked in #perl-help
(Mithaldu) mib_4ql3ih: given that it's an xs module my guess would be it isn't
¹¹¹º Quit» (mib_4ql3ih) (5e8eeaad@ircip1.mibbit.com) (Quit: http://www.mibbit.com ajax IRC Client)

Or if they're lucky like this:

(solidblanc) What can I do about "sysread() is deprecated on :utf8 handles at C:/Strawberry/perl/vendor/lib/File/Slurp.pm line 225."
(Mithaldu) solidblanc: probably use File::Slurp less, if you can help it
(Mithaldu) also that's a question that's fine for #perl-help
(Mithaldu) solidblanc: IO::All or Path::Tiny are much better replacements
(solidblanc) ok, i'll tell the bugzilla folks :P Thx
(Mithaldu) solidblanc: good luck with that. maybe also google. maybe someone found a solution already
(Mithaldu) solidblanc: (dylan) Mithaldu: tell him bugzilla won't be producing that error as soon as the patch that removes File::Slurp lands.
(Mithaldu) from #perl-help

I can't remember the last time an actual windows-specific question was asked. I can't remember anyone ever actually going to #perl-help when told.

Part of the problem is that even though #win32 points people at #perl-help, people who come there generally have no idea what the hell irc is and how to join channels.

Making the first link they encounter be the #perl-help channel would drastically increase the chances of people actually getting help.

[frioux]

Agreed. #win32 is fine but really for win32 specific stuff preferably.

[haarg]

+1

[wchristian]

And i see it live. Many many thanks, kmx! :D