Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Why Does Windows Use Backslash as Path Separator?. Parent comment
It is pretty powerful/insane that stuff like this is a part of PowerShell and that's probably what the GP is talking about:
Add-Type -TypeDefinition @" using System; namespace DemoCode { public class DemoClass { public static void WriteHello() { Console.WriteLine("Hello"); } } } "@ [DemoCode.DemoClass]::WriteHello()
It blurs the lines as to what it is no matter how you look at it.
In contrast, try doing that in cmd.exe or invoking a function from a shared object after getting a pointer to it using dlopen through a POSIX shell.
[0] - https://www.powershellgallery.com/packages/PSReflect-Functio...
[1] - https://fuzzysecurity.com/tutorials/24.html
There are no comments on this comment yet.
It is pretty powerful/insane that stuff like this is a part of PowerShell and that's probably what the GP is talking about:
Or LoadLibrary call and invocation from PowerShell. [0] [1]It blurs the lines as to what it is no matter how you look at it.
In contrast, try doing that in cmd.exe or invoking a function from a shared object after getting a pointer to it using dlopen through a POSIX shell.
[0] - https://www.powershellgallery.com/packages/PSReflect-Functio...
[1] - https://fuzzysecurity.com/tutorials/24.html