bugDDD - Bugs: bug #31255, perl hash key incorrectly parsed...

 
 

bug #31255: perl hash key incorrectly parsed for display of item value

Submitter:  Rob Retter <rretter>
Submitted:  Tue 05 Oct 2010 05:26:02 PM UTC
 
Category:  Data display Severity:  3 - Normal
Item Group:  None Status:  Wont Fix
Privacy:  Public Assigned to:  None
Open/Closed:  Closed Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Wed 28 Dec 2022 06:39:16 PM UTC, comment #1: 

perl is no longer supported by DDD

Stefan Eickeler <eickeler>
Project Administrator
Tue 05 Oct 2010 05:26:02 PM UTC, original submission:  

When a Perl hash element happens to have a string such as:

'hi.there'

for its hash key, and that hash is being Displayed in the data window, one may right-click on the element to bring up a new Display of the item value.

Doing so is necessary only when the item value is an array reference or other such indirect value, because a simple scalar value would already appear in the original hash Display.

But let's say you do have a hash element whose value involves indirection and you try to launch a new "sub"-Display of the hash element's value.  What gets displayed is not $hash{'hi.there'} but rather $hash{'there'}.  And that hash elem is usually undefined.

It seems like the dot char '.' within the hash key string confuses ddd and causes it to then treat the hash value as residing at an incorrect slot in the hash.  Namely one whose key is only the "trailing" portion of the key string (the portion following the last dot).  The right behavior would be to use all of the string, not just that trailing portion.

Rob Retter <rretter>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by eickeler (Updated the item)
  • -email is unavailable- added by rretter (Submitted the item)
  • -email is unavailable- added by rretter
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-12-28 eickeler StatusNone Wont Fix
    2022-12-28 eickeler Open/ClosedOpen Closed
    2010-10-05 rretter Carbon-Copy- Added rretter

    Back to the top

    Powered by Savane 3.9