<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Using $@ in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922120#M286076</link>
    <description>&lt;!--!*#--&gt;Hi Manuales,&lt;BR /&gt;&lt;BR /&gt;From sh-posix(1):&lt;BR /&gt;&lt;BR /&gt;      The meanings of $* and $@ are identical when not quoted or when used&lt;BR /&gt;      as a parameter assignment value or as a file name.  However, when used&lt;BR /&gt;      as a command argument, "$*" is equivalent to "$1d$2d...", whereas "$@"&lt;BR /&gt;      is equivalent to "$1"d"$2"d... (where d is the first character of&lt;BR /&gt;      IFS),      The special meaning of keywords or aliases can be removed by quoting&lt;BR /&gt;      any character of the name.  The recognition of function names or&lt;BR /&gt;      special command names cannot be altered by quoting them.&lt;BR /&gt;&lt;BR /&gt;PCS&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 08 Jan 2007 08:55:46 GMT</pubDate>
    <dc:creator>spex</dc:creator>
    <dc:date>2007-01-08T08:55:46Z</dc:date>
    <item>
      <title>Using $@</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922118#M286074</link>
      <description>Hi, what is the meaning of: $@ ?&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Sun, 07 Jan 2007 19:03:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922118#M286074</guid>
      <dc:creator>Manuales</dc:creator>
      <dc:date>2007-01-07T19:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: Using $@</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922119#M286075</link>
      <description>To tell about $@ I am telling two commands which is looking like similar but with little bit difference.&lt;BR /&gt;&lt;BR /&gt;$* : Collectively references all the positional parameters as $1, $2, ...&lt;BR /&gt;&lt;BR /&gt;$@ : Same as $*, except when double-quoted ("$@") collectively references all the positional parameters as "$1", "$2", ...&lt;BR /&gt;&lt;BR /&gt;Remember in both the cases you cannot reassign the Parameter values.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Nitin</description>
      <pubDate>Mon, 08 Jan 2007 08:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922119#M286075</guid>
      <dc:creator>Nitin Kumar Gupta</dc:creator>
      <dc:date>2007-01-08T08:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: Using $@</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922120#M286076</link>
      <description>&lt;!--!*#--&gt;Hi Manuales,&lt;BR /&gt;&lt;BR /&gt;From sh-posix(1):&lt;BR /&gt;&lt;BR /&gt;      The meanings of $* and $@ are identical when not quoted or when used&lt;BR /&gt;      as a parameter assignment value or as a file name.  However, when used&lt;BR /&gt;      as a command argument, "$*" is equivalent to "$1d$2d...", whereas "$@"&lt;BR /&gt;      is equivalent to "$1"d"$2"d... (where d is the first character of&lt;BR /&gt;      IFS),      The special meaning of keywords or aliases can be removed by quoting&lt;BR /&gt;      any character of the name.  The recognition of function names or&lt;BR /&gt;      special command names cannot be altered by quoting them.&lt;BR /&gt;&lt;BR /&gt;PCS&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jan 2007 08:55:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using/m-p/3922120#M286076</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2007-01-08T08:55:46Z</dc:date>
    </item>
  </channel>
</rss>

