RobertKaucher wrote: » I agree with JDMurray, but hey! PowerShell is Object Oriented and is able to access .Net objects!
JDMurray wrote: » Does PowerShell's scripting language really support classes with true polymorphism, inheritance, and encapsulation? Just because PowerShell cmdlets are .NET classes doesn't make PowerShell's scripting language Object-Oriented. I see nothing about OO Design in the MSDN Windows PowerShell Blog. If it's OO you be wanting (matey) then it's C# or Java for you! (R)
$fw = new-object -com HNetCfg.FwMgr $profile = $fw.LocalPolicy.CurrentProfile $profile.GloballyOpenPorts | ft name, port
RobertKaucher wrote: » Perhaps Object-Oriented Scripting, rather than Object-Oriented Programming?
dynamik wrote: » Can we just call it an object-oriented scripting language and remain friends?
RobertKaucher wrote: » Is there a term that better describes languages like PowerShell? Object Consumer Language? That's just ugly.
JDMurray wrote: » Objects are dynamic and can contain both code and data. Using this description, any running process with an interface can be considered an object. Therefore, any scripting language can be considered object-based, yet still not object-oriented. This really shows how both abstract and overloaded the computer science term "object" has become.