At 09:02 PM 5/28/00, Matthew Persico wrote: >MS isn't. Sounds to me like AS is doing all the work, attaching to MS's >apis. Maybe you can thank US Justice Dept for even getting MS to be >cooperative. You're right. I just think that MSifying (is that a word) Perl is inevitable if it heads into Visual Studio. MS and open standards just do not mix. Kerberos on Win2000 proves this. Check out Inter@ctive Week for more info on that. It was in it a few weeks back. Greg --- You are currently subscribed to perl-win32-users as: [archive@jab.org] To unsubscribe, forward this message to [EMAIL PROTECTED] For non-automated Mailing List support, send email to [EMAIL PROTECTED]
- Visual Perl in Visual Studio Paul Rogers [CE]
- Re: Visual Perl in Visual Studio Emo1313
- Re: Visual Perl in Visual Studio Matthew Persico
- Re: Visual Perl in Visual Studio Paul Rogers [CE]
- Re: Visual Perl in Visual Studio Matthew Persico
- Re: Visual Perl in Visual Studio Paul Rogers [CE]
- RE: Visual Perl in Visual Studio alan.swan
- Re: Visual Perl in Visual Studio Matthew Persico
- Re: Visual Perl in Visual Studio Gregory Bair
- Re: Visual Perl in Visual Studio Robert White
- Re: Visual Perl in Visual Studio Jan Dubois
- RE: Visual Perl in Visual Studio Joe Schell
- Re: Visual Perl in Visual Studio Jan Dubois
- Re: Visual Perl in Visual Studio Simon Oliver
- RE: Visual Perl in Visual Studio alan.swan
- Re: Visual Perl in Visual Studio Mihail Belanov
- Re: Visual Perl in Visual Studio Philip Newton
- Re: Visual Perl in Visual Studio Paul Rogers [CE]
- Re: Visual Perl in Visual Studio Jan Dubois