From: "Paul Rogers [CE]" <[EMAIL PROTECTED]>
> Well, I think it was a reference to Visual Perl as it will be included in
> Visual Studio, which itself includes Visual C++.
Well, my VS includes Visual Basic instead. Blew the C++ away after
getting tired of 100 meg of fat I wasn't using. A Perl plugin for VS might
be interesting, somewhere around version 2 I'd expect. :-)
Of more immediate benefit is an IDE for newbies soaking up some of the
beginner questions. A menu item to search the ActiveState mailing lists
wouldn't hurt either. They'll have to integrate running a web server in
there too ,,,,, the PWS questions will disappear (mostly, maybe, hopefully
:-).
And just imagine (!!!) Active Update for Perl FAQs! Very useful when a
new version of whatever is just a lil' bit broken. (just check 'yes look for
new stuff at AS every time I boot', yes indeed :-)))
From: "Gregory Bair" <[EMAIL PROTECTED]>
> 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.
Perl ain't Kerberos. (how many of you heard of Kerberos before that blew
up, raise hands). And micro~1 isn't doing the work. AS is. That's just
enough of a difference to make a difference.
For Microsoft to screw around in the (AS) core distro they actually need
a reason (any reason, some kind of rationale) to 'extend' and I don't really
see one. They want a paperclip? use Win32::API; Something else? XS and
make a dll. Anybody with something solid on this instead of paranoid
mutterings please bring it out.
The Extend may, in fact, go in the other direction, hacking the OS to
accomodate Perl. Alarm, anyone?
Rob
http://bangkokwizard.com/
I can't be alarmed about this,
I can't even signal distress!
---
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]
