Inline as defined by Merriam-Webster's dictionary is a word on its own:

having the parts or units arranged in a straight line

Inline and line are contextual terms in IT and CS (much like host is).

Even in this case, a line has 2 meanings: a line of text as displayed in the terminal (subject to overflow), and a line as read by the powershell engine when executing statements (terminated by one of powershell's line terminators: \r?\n, ; or })

It's only confusing, if you have ever used the term in one context.

Consider the following:

In most programming languages, this type of statement is considered in-line as the entire thing is evaluated as a singular unit terminated by that language's line endings:

$value = (& {
    "Despite this scriptblock taking multiple lines of space,"
    "it is all contained within the wrapping parenthesis,"
    "and terminated by the following colon"
}); # <- the actual line-terminator as interpreted by PowerShell

or in javascript, the IIFE pattern:

var value = (() => {
    return [
        "Despite this function taking multiple lines of space,",
        "it is all contained within the wrapping parenthesis,",
        "and terminated by that last colon"
    ];
})(); // <- the actual line-terminator as interpreted by JS

The engine may see IIFE-esque patterns as multiple lines, but the entire encapsulating statement is evaluated as a single line

Inline Splatting Meta Issue #25721

Description

RFCs

Issues

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions