On Sat Dec 16 14:35:24 2006, [EMAIL PROTECTED] wrote:
> Affected files:
>
> /README.win32.pod
>
> ...
>
Applied in r16187, thanks!
Jonathan
Ron Blaschke wrote:
Seems like the old Visual C++ Toolkit 2003 is discontinued.
http://msdn2.microsoft.com/en-us/visualc/aa336490.aspx
Aha. If you would have a moment to write these latest changes into
readme.win32.pod and send in a patch, that'd be awesome; otherwise I'll
get to it when I
On 12/16/06, [EMAIL PROTECTED] via RT <[EMAIL PROTECTED]> wrote:
On Sat Nov 11 11:53:27 2006, [EMAIL PROTECTED] wrote:
> Not sure if this is a bug or not, but I noticed that the open opcode
> creates its argument if the desired file doesn't exist.
>
There are two variants of the open opcode: this
> On Mon Nov 20 06:24:00 2006, stmpeters wrote:
> > It took some tweaking to get some of the warnings shut off, but the
> > attached patch actually gets the files to compile, although it doesn't
> > actually build a parrot to test with. Expect a few more patches over
> the
> > next week to finish
On Sun Dec 17 19:29:46 2006, [EMAIL PROTECTED] wrote:
> With ICU optional these days, is this still necessary?
I have a Visual C++ Toolkit 2003 lying around (I think), so, if I do,
I'll give this a try along with my Borland work.
On Dec 18, 2006, at 1:57 AM, Paul Cochrane wrote:
Be aware that you cannot use the verbose form of Emacs settings at
the beginning of a file, unless the file is shorter than 3000 bytes.
See Perl::Critic::Policy::Editor::RequireEmacsFileVariables policy
for more details:
So this means we need t
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to
complete your request.
Please contact the server administrator, [EMAIL PROTECTED] and inform them of
the time the error occurred, and anything you might have done that may have
caused the error.
Jonathan Worthington wrote:
> chromatic via RT wrote:
>> With ICU optional these days, is this still necessary?
>>
> Since Windows doesn't ship with a C compiler and this toolkit is one of
> the easiest ways to get hold of one for free, then yes, it's good to
> have it documented. (It may be *ca
chromatic via RT wrote:
With ICU optional these days, is this still necessary?
Since Windows doesn't ship with a C compiler and this toolkit is one of
the easiest ways to get hold of one for free, then yes, it's good to
have it documented. (It may be *called* the C++ toolkit, but it's also
Thanks! Applied in r16183.
10 matches
Mail list logo
