[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HV and SV problem
From: |
Gavin Smith |
Subject: |
Re: HV and SV problem |
Date: |
Fri, 6 Jun 2025 19:53:01 +0100 |
On Fri, Jun 06, 2025 at 07:27:56PM +0100, Gavin Smith wrote:
> I had a breakthrough when I realised that the referenced parent element,
> the $previous_ending_container->{'contents'}->[$i]->{'parent'}, was the
> before_item
> element that was being overwritten. What if the assignment didn't just
> change the
> value for 'parent' in the hash
> (%{$previous_ending_container->{'contents'}->[$i]}),
> but modified the object that was referenced?
To clarify this point, it is not that the referenced hash itself is modified,
but the reference to that hash is overwritten, and that overwritten reference
is shared by another part of the data structure.
- Duplicate variable use in Texinfo/ManipulateTree.pm, Gavin Smith, 2025/06/04
- Re: Duplicate variable use in Texinfo/ManipulateTree.pm, Patrice Dumas, 2025/06/04
- Re: Duplicate variable use in Texinfo/ManipulateTree.pm, Gavin Smith, 2025/06/05
- Re: Duplicate variable use in Texinfo/ManipulateTree.pm, Patrice Dumas, 2025/06/05
- HV and SV problem, Gavin Smith, 2025/06/06
- Re: HV and SV problem, Gavin Smith, 2025/06/06
- Re: HV and SV problem,
Gavin Smith <=
- Re: HV and SV problem, Patrice Dumas, 2025/06/07
- Re: HV and SV problem, Patrice Dumas, 2025/06/07
- Re: HV and SV problem, Gavin Smith, 2025/06/07
- Re: HV and SV problem, Gavin Smith, 2025/06/07