Re: Future of Perl on Win32?

Humm... Is possible Microsoft don't like Perl because it have their Perl?

Today, Microsoft has released RC1 version of PowerShell the .NET-based shell with perl-like syntax... More...

Example:

$compsys = get-wmiObject win32_computersystem
$biosinf = get-wmiObject win32_bios
$netinfo = get-wmiObject win32_networkadapter | 
where-object { $_.adaptertype -like "802.3" }
$cdrom   = get-wmiObject win32_cdromdrive

"Make  = " + $compsys.manufacturer
"Model = " + $compsys.model
"Bios  = " + $biosinf.name + " " + $biosinf.smbiosbiosversion
foreach ( $nic in $netinfo ) { "NIC   = " + $nic.name }
foreach ( $cd in $cdrom )    { "CDROM = " + $cd.name }
[download]

Extracted from PowerShell User Guide:
Special Variables
$_ The current pipeline object; used in script blocks, filters, the process clause of functions, where-object, foreach-object and switch.

Special Variables
$_	The current pipeline object; used in script blocks, filters, the process clause of functions, where-object, foreach-object and switch.

Ugly notation! :-)

Asociative Array: $<array name> = @{<key1 = item1>; <key2 = item2>;...}

Comment on Re: Future of Perl on Win32? Select or Download Code

Replies are listed 'Best First'.
Re^2: Future of Perl on Win32? by explorer (Chaplain) on Apr 26, 2006 at 16:25 UTC
I am reading the User Guide. Page 38: We investigated a number of different options; whether to extend the current CMD.EXE syntax or to modify the current Visual Basic to better enable an interactive use. After looking at many different possibilities, we decided that a new language that was built from the ground up would be best because it would enable us to provide a more consistent environment. We were inspired by concepts in the UNIX shells; other scripting languages such as PERL, PHP, PYTHON and programming languages like C# to create a consistent, intuitive language that is an interactive environment. Page 72: Similar to the UNIX model, the majority of users will find that the use of commands is sufficient to accomplish what is required. However, there are conditions when existing commands do not provide the required functionality. In these cases, there are generally two choices. First, if the functionality is able to be composed, create a script to provide the necessary functionality. Second, create a new command to provide the needed functionality (much in the same way that the functionality of text parsing utilities for the UNIX system have increased over time and is arguable why PERL, TCL, and other scripting languages developed). Unfortunately, the complexity of creating a new command can be high, and in some cases, the required tools (such as a compiler) are not available. For the records... Perl is named 6 times. C#, 14. Java, 0. TCL, 2. Python, 2. Ruby, 1.	[reply]
Re^3: Future of Perl on Win32? by demerphq (Chancellor) on Apr 26, 2006 at 17:41 UTC
Somebody should point out that they need to do a `s/PERL/Perl/` :-) --- $world=~s/war/peace/g	[reply] [d/l]
Re^3: Future of Perl on Win32? by chanio (Priest) on Apr 26, 2006 at 23:50 UTC
(add this) We investigated a number of different options; whether to extend the current CMD.EXE syntax or to modify the current Visual Basic to better enable an interactive use... INTERIX: M$ Linux ...But something's missing :) ... Landlords production is only eaten by landlords... Wherever I lay my KNOPPIX disk, a new FREE LINUX nation could be established	[reply]
Re^2: Future of Perl on Win32? by bioMan (Beadle) on Apr 26, 2006 at 20:09 UTC
Looks like the misbegotten love child of Perl, Python, and VB. Mike	[reply]