Re: Seemingly enigmatic data structures

Linda,

In this context using arrays and hashes, the -> operator:

must

It must be used to access the first data structure level of a reference to an array:

my $ra_staff = \@staff;
$ra_staff->[0]...
[download]

must not

It must not be used to access the first data structure level of an array:

$staff[0]...
[download]

may

It is optional everywhere else: as shown by lidden above.

Regards,

PN5

Comment on Re: Seemingly enigmatic data structures Select or Download Code

Replies are listed 'Best First'.
Re^2: Seemingly enigmatic data structures by tphyahoo (Vicar) on Mar 05, 2005 at 12:16 UTC
must be used in one place must not be used in one place isn't this a contradiction? UPDATE: Ah, OK, I get it now, more or less. Though I do think that could have been more clearly worded. "...first data structure level of a reference" is pretty gibberishy to me. But the examples make it more or less clear.	[reply]
Re^3: Seemingly enigmatic data structures by merlyn (Sage) on Mar 05, 2005 at 13:55 UTC
Another simpler rule is: Arrows are optional between subscripty kinds of things (brackets, braces, parens). -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
Re^4: Seemingly enigmatic data structures by tphyahoo (Vicar) on Mar 05, 2005 at 17:39 UTC
Thinking "between" helps. But wouldn't that just be brackets and braces? Where are arrows optional between parens?	[reply]
Re^5: Seemingly enigmatic data structures by Joost (Canon) on Mar 05, 2005 at 18:01 UTC