From @nwc10

This is a meta-ticket to tag issues in the perl core which need attention on
Win32.

See also Win32 This is a meta-ticket to tag issues in the perl core which need attention on Win32. See #11925

It's for keeping track of outstanding problems which need manual inspection
and correction on Win32, rather than simply test failures which can be
resolved by inspecting the diagnostics in automatic smoker logs and
testing potential fixes by pushing to a smoke-me branch. The intent is that
things that have stalled, or things that are obviously "hard" belong here,
not that every Win32 ticket is attached and then closed.

In particular​:

* Problems that need investigation at the C level in a debugger
* Problems involving the Win32 API

which the vast majority of core committers and active contributors can't
resolve because they have neither access nor the domain knowledge.

That list probably isn't exhaustive.

Nicholas Clark

From @bulk88

#11692

The RT System itself - Status changed from 'new' to 'open'

From @bulk88

Add #12288 and #12276

From @bulk88

Add #11267

From @Leont

On Thu, Feb 2, 2012 at 4​:26 PM, Nicholas Clark
<perlbug-followup@​perl.org> wrote​:

This is a meta-ticket to tag issues in the perl core which need attention on
Win32.

It's for keeping track of outstanding problems which need manual inspection
and correction on Win32, rather than simply test failures which can be
resolved by inspecting the diagnostics in automatic smoker logs and
testing potential fixes by pushing to a smoke-me branch. The intent is that
things that have stalled, or things that are obviously "hard" belong here,
not that every Win32 ticket is attached and then closed.

In particular​:

* Problems that need investigation at the C level in a debugger
* Problems involving the Win32 API

which the vast majority of core committers and active contributors can't
resolve because they have neither access nor the domain knowledge.

That list probably isn't exhaustive.

We should probably add a ticket for the :win32 PerlIO layer. It seems
no one really knows what the state of it is, though it's rumored to be
buggy. I would expect native IO primitives to be preferable to the
POSIX layer we're using now.

Leon

From @demerphq

On 2 February 2012 15​:26, Nicholas Clark <perlbug-followup@​perl.org> wrote​:

which the vast majority of core committers and active contributors can't
resolve because they have neither access nor the domain knowledge.

$work was supposed to solve access. Domain knowledge I leave to others.

Ill chase up and see what the story is.

Yves

--
perl -Mre=debug -e "/just|another|perl|hacker/"

From dennis.kaarsemaker@booking.com

On ma, 2012-08-06 at 18​:02 +0200, demerphq wrote​:

On 2 February 2012 15​:26, Nicholas Clark <perlbug-followup@​perl.org> wrote​:

which the vast majority of core committers and active contributors can't
resolve because they have neither access nor the domain knowledge.

$work was supposed to solve access. Domain knowledge I leave to others.

Ill chase up and see what the story is.

Box is there, but I don't know how to best give access. Have it smoke
blead and smoke-me/* or cygwin ssh? User account maintenance on it is
annoying, so I'd like to limit the number of users on it.

--
Dennis Kaarsemaker, Systems Architect
Booking.com
Herengracht 597, 1017 CE Amsterdam
Tel external +31 (0) 20 715 3409
Tel internal (7207) 3409

From @jandubois

On Mon, 06 Aug 2012, Leon Timmermans wrote​:

We should probably add a ticket for the :win32 PerlIO layer. It seems
no one really knows what the state of it is, though it's rumored to be
buggy. I would expect native IO primitives to be preferable to the
POSIX layer we're using now.

I remember reading a message from Nick Ing-Simmons that the :win32 layer
was 80% finished, but can't find the message anymore.

Cheers,
-Jan

From offer.kaye@gmail.com

On Mon, Aug 6, 2012 at 11​:27 PM, Jan Dubois wrote​:

I remember reading a message from Nick Ing-Simmons that the :win32 layer
was 80% finished, but can't find the message anymore.

http​://www.nntp.perl.org/group/perl.xs/2004/08/msg1629.html

Regards,
Offer

From @bulk88

#9719, #6704, #9025

From @bulk88

add #7714 please. It is not a trivial fix for me.

From @wchristian

Please add #14414

This whole ticket looks like what a label should be used for.