This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

pending/1525: "struct target_ops" -> "struct gdbtarg" || "struct target"


>Number:         1525
>Category:       pending
>Synopsis:       "struct target_ops" -> "struct gdbtarg" || "struct target"
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Mon Jan 19 20:08:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Hello,
 
 The current "target_ops" structure appeared with GDB 4.  The original 
 implementation containing only methods.  Since then the target_ops have 
 evolved to include data vis:
 
      struct section_table
       *to_sections;
      struct section_table
       *to_sections_end;
 
 I think, the vector should be re-named to "struct target" or "struct 
 gdbtarg" (consistent with gdbarch, and more name space proof) so that it 
 correctly reflects its current implementation.
 
 I'd like to do this now, before the target methods start being 
 explicitly parameterized with their target vector.
 
 thoughts?
 Andrew
 
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]