PowerShell is a very interesting and powerful language, which also borrowed many aspects from Perl and some from Haskell.

I never worked with PowerShell, except for casting a few magic spells copied from Google results to make Windows behave.

• Interesting b/c instead of piping text, they are piping objects (in the first draft the language was named "Monad")
• Powerfull because these object have deep access into the OS and .NET-framework.

That should allow doing interesting things WITHIN the PowerShell/.NET walled garden. As long as you can use those objects, everything should be fine (except for bugs). But what about Unix-style interactions with other programs? Piping objects arounds surely is a powerful concept, but can I stuff binary data from STDOUT of tool A into a pipe, then filter it through B, C, D, and finally have E process the result of filtering? (In other words, what's the equivalent of a bash on Unix doing A -foo -bar | B -bla bla | C --what=ever | D ./magic ./stuff  | E +gnarf)

What about networking? I often do things like this:

(Create a tar archive of subtree in /some/where and write to STDOUT, have ssh pass that byte stream to another tar instance running as root on embedded.system as STDIN, make that second tar extract the archive to /else/where, write STDOUT of the second tar to copied.txt on the local system, and STDERR to problems.txt on the local system.)

What about quoting? Quoting the two redirections in the previous command would write STDOUT and STDERR of the second tar to embedded.system, because ssh implicitly invokes a shell on embedded.system:

How to pass things like ", ', <, >, | as arguments? On Unix:

Expanding variables, and passing parameters that just look like variable expansions?

Alexander

Well... Tell me! :)

With the exception of ssh all of this should be possible, Win has another approach here.

update

Looks like win10 comes with a ssh server. Haven't used it yet.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

In PS you'll transport a list of objects , e.g. the file-size is just an attribute of one of the file-objects 

that's interesting, I was not aware. Actually it sounds impressive but in reality is nothing more than a unix-like pipe communication passing a text-json-pojo-whatever or, as easily, binary-data to, e.g., represent serialized objects. Both can be and are achieved in unix. Text-pipes we are all aware of and for binary: an example is imagemagick's piping of binary images to its various converter-executables.

This however poses some more interesting questions: for example are these objects allowed to have pointers to other objects? Surely there is inter-linkage. For example a file object with pointers to the object of its user-owner which in turn will have pointers to history-object and preferences-object and a myriad of other details? Often saucy and often remotely stored? Oh that's lovely, I can suck the whole M$-big-brother-brain with just an ls. and God said let there be ls. I can imagine that with just an ls I can suck each and every digital record ever existed.

Further, when do these objects expire/die/cleared from memory? It seems that there is a gargantuan garbage collector larking at the bowels of the OS? And is very busy indeed. With each innocent find c:/*.*|grep which could potentially copy the whole hard-disk's contents into RAM and then back to disk-swap to feed back find. Here's a nice blue screen of death right there.

Anyway, some thoughts. now, begin-trolling:

Nah... M$ is thoughtless crap (disclaimer: If trump was voted in as USA president then I am allowed an aphorism for each of them votes).

end-trolling

bw, bliako

> for example are these objects allowed to have pointers to other objects?

yes, a little demo

 
PS C:\tmp> ls tst                                         # stringific
+ation of list of objects


    Verzeichnis: C:\tmp


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       22.01.2021     01:23             12 tst


PS C:\tmp> (ls tst).GetAccessControl().Owner              # get Access
+ Obj and get owner
COM\RolfLanX
PS C:\tmp> $x=ls tst                                      # save obj i
+n var 
PS C:\tmp> $x.length                                      
6
PS C:\tmp> cat tst

PS C:\tmp> echo "blabla" >tst                             # change con
+tent
PS C:\tmp> $x.length                                      # old length
6
PS C:\tmp> (ls tst).length                                # new length
18
[download]

I also already found a caveat

PS C:\tmp> (ls tst*).name           # name for each list element
tst
tst.pl
tst.txt
tst_flushing.pl
tst_flushing.pl~
tst_onclick.html
tst_onclick.html~
tst_pde.pl
tst_pde.pm
tst_pde.pm~
PS C:\tmp> (ls tst*).length         # length of list not list elements
10
[download]

NB: The "cmdlet" Get-ChiltItem (aka ls) can list very different types of objects, not only filesystem.

PS C:\tmp> ls -Path HKLM:\HARDWARE


    Hive: HKEY_LOCAL_MACHINE\HARDWARE


Name                           Property
----                           --------
ACPI
DESCRIPTION
DEVICEMAP
RESOURCEMAP
UEFI

PS C:\tmp> cd -Path HKLM:\HARDWARE         # cd into registry
PS HKLM:\HARDWARE> ls -name                # list names
ACPI
DESCRIPTION
DEVICEMAP
RESOURCEMAP
UEFI
PS HKLM:\HARDWARE>
[download]

TIMTOWTDI, this is was all done without even piping.

You might wanna consult a tutorial, I only scratched the surface so far. :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

ok thanks, it's all new to me. And I found a couple of related modules on CPAN. The dir-style for options also appears in Linux (e.g. /proc) don't know which was there first.