{"id":8711,"date":"2007-01-23T17:00:30","date_gmt":"2007-01-23T17:00:30","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2007\/01\/23\/array-literals-in-powershell\/"},"modified":"2019-02-18T13:20:50","modified_gmt":"2019-02-18T20:20:50","slug":"array-literals-in-powershell","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/array-literals-in-powershell\/","title":{"rendered":"Array Literals In PowerShell"},"content":{"rendered":"

The first thing to understand is that there are no array literals in PowerShell J<\/span> Arrays are built using operators or casts. The way to build an array in PowerShell is to use the comma operator as shown in the following examples:\n<\/span><\/p>\n

\n\u00a0<\/p>\n

$a = , 1\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0# array of one element\n<\/span><\/p>\n

$a = 1,2 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0# array of two elements\n<\/span><\/p>\n

$a = 1,2,3 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0# array of three elements.\n<\/span><\/p>\n

$a = (1,2),(3,4) \u00a0# array of two elements, each of which is a two element array\n<\/span><\/p>\n

$a += ,(5,6)\u00a0\u00a0\u00a0\u00a0\u00a0 # add another element which is an array of two element.\n<\/span><\/p>\n

\n\u00a0<\/p>\n

Now let’s display the array we’ve built. Simply displaying the variable isn’t very helpful since PowerShell will unravel everything in the display process obscuring the inner structure. Instead we’ll use individual indexing operations to look at each piece:\n<\/span><\/p>\n

\n\u00a0<\/p>\n

PS (61) > $a[0]\n<\/span><\/p>\n

1\n<\/span><\/p>\n

2\n<\/span><\/p>\n

PS (62) > $a[1]\n<\/span><\/p>\n

3\n<\/span><\/p>\n

4\n<\/span><\/p>\n

PS (63) > $a[2]\n<\/span><\/p>\n

5\n<\/span><\/p>\n

6\n<\/span><\/p>\n

\n\u00a0<\/p>\n

The comma operator is the array construction operator in PowerShell (similar to the cons function in LISP.)\n<\/span><\/p>\n

\n\u00a0<\/p>\n

By now, if you’re familiar with PowerShell, you’re asking \u2013 so what’s with the @() notation? If it isn’t an array literal, then what is it? First let’s talk about arrays and casts. The other way to build an array is through a covariant conversions or casts. In PowerShell, this includes the ability to cast a scalar object into an array. In the following example, we’re casting an integer into an array:\n<\/span><\/p>\n

\n\u00a0<\/p>\n

PS (64) > $a = [array] 1\n<\/span><\/p>\n

PS (65) > $a[0]\n<\/span><\/p>\n

1\n<\/span><\/p>\n

\n\u00a0<\/p>\n

Now, since it’s already an array, casting it again doesn’t result in a second level of nesting:\n<\/span><\/p>\n

\n\u00a0<\/p>\n

PS (66) > $a = [array] [array] 1\n<\/span><\/p>\n

PS (67) > $a[0]\n<\/span><\/p>\n

1\n<\/span><\/p>\n

\n\u00a0<\/p>\n

However using 2 commas *does<\/strong>* nest the array since it is the array construction operation:\n<\/span><\/p>\n

\n\u00a0<\/p>\n

PS (68) > $a = ,,1\n<\/span><\/p>\n

PS (69) > $a[0][0]\n<\/span><\/p>\n

1\n<\/span><\/p>\n

\n\u00a0<\/p>\n

Now on to @(). In essence, the @( \u2026 ) operation is syntactic sugar for\n<\/span><\/p>\n

\n\u00a0<\/p>\n

[array] $( \u2026 )\n<\/span><\/p>\n

\n\u00a0<\/p>\n

\u00a0So \u2013 if the statements in @() return a scalar, it will be wrapped in an array but if the result is already an array, then it won’t be nested.\n<\/span><\/p>\n

\n\u00a0<\/p>\n

And finally, why did we do it this way? The goal was to make array operations consistent with the command argument syntax. A comma on the command line indicates a collection of objects bound to one parameter.\n<\/span><\/p>\n

\n\u00a0<\/p>\n

PS (77) > function f([array] $x, [array] $y, [array] $z) {$x.count; $y.count, $z.count}\n<\/span><\/p>\n

PS (78) > foo a,b,c z l,m\n<\/span><\/p>\n

3\n<\/span><\/p>\n

1\n<\/span><\/p>\n

2\n<\/span><\/p>\n

\n\u00a0<\/p>\n

And why have @() at all? Because pipelines in a value context gather their results from a stream. From the stream you can’t tell whether the pipeline returned a singleton or a collection. Using the @() means that you don’t really have to care. If you might receive a collection, then just use\n<\/span><\/p>\n

\n\u00a0<\/p>\n

$result = @( \u2026 pipeline \u2026 )\n<\/span><\/p>\n

\n\u00a0<\/p>\n

and it doesn’t matter what you receive, it will always be an array.\n<\/span><\/p>\n

\n\u00a0<\/p>\n

-bruce\n<\/span><\/p>\n

\n\u00a0<\/p>\n

Bruce Payette [MSFT]\n<\/span><\/p>\n

Windows PowerShell Tech Lead\n<\/span><\/p>\n

\n\u00a0<\/p>\n

Visit the Windows PowerShell Team blog at: <\/span>http:\/\/blogs.msdn.com\/PowerShell\n\t\t<\/span><\/p>\n

Visit the Windows PowerShell ScriptCenter at: <\/span>http:\/\/www.microsoft.com\/technet\/scriptcenter\/hubs\/msh.mspx\n\t\t<\/span><\/p>\n

Windows PowerShell in Action (book): <\/span>http:\/\/manning.com\/powershell\n\t\t<\/span><\/p>\n

\n\t\t<\/span>\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"

The first thing to understand is that there are no array literals in PowerShell J Arrays are built using operators or casts. The way to build an array in PowerShell is to use the comma operator as shown in the following examples: \u00a0 $a = , 1\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0# array of one element $a = […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"

The first thing to understand is that there are no array literals in PowerShell J Arrays are built using operators or casts. The way to build an array in PowerShell is to use the comma operator as shown in the following examples: \u00a0 $a = , 1\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0# array of one element $a = […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/8711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=8711"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/8711\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=8711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=8711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=8711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}