RE: Merge gdbarch.sh and doc/gdbint.texinfo?

RE: Merge gdbarch.sh and doc/gdbint.texinfo?

[Zaretskii Eli]

This message was scanned for viruses and other malicious code by PrivaWall.


This mail was sent from ELTA SYS LTD.


> From: Andrew Cagney [mailto:ac131313@redhat.com] 
> Sent: Wednesday, February 19, 2003 3:06 PM
> 
> > As a kind of related side effect, what do people think of 
> making the architecture vector table an appendix.  That way 
> it doesn't clutter up the core internals documentation.
> 
> What about this?  My guess at what to do next is:
> 
> - move the arch vector to the appendix and make it a separate file
> - change it to use that weird @defun texi thingie
> - add in the missing methods
> - finally start worrying about the doco

Fine with me.


This message is processed by the PrivaWall Email Security Server. 

RE: Merge gdbarch.sh and doc/gdbint.texinfo?

[Zaretskii Eli]

This message was scanned for viruses and other malicious code by PrivaWall.


This mail was sent from ELTA SYS LTD.


> From: Andrew Cagney [mailto:ac131313@redhat.com] 
> Sent: Tuesday, February 18, 2003 11:45 PM
> 
> What do people think of moving gdbarch.sh's table of methods into 
> gdbinit.texinfo and have gdbarch.sh extract them from there?

I'm all for it.


This message is processed by the PrivaWall Email Security Server. 

Re: Merge gdbarch.sh and doc/gdbint.texinfo?

[Andrew Cagney]

(yes I probably should have sent this to gdb@)


>> From: Andrew Cagney [mailto:ac131313@redhat.com] 
>> Sent: Tuesday, February 18, 2003 11:45 PM
>> 
>> What do people think of moving gdbarch.sh's table of methods into 
>> gdbinit.texinfo and have gdbarch.sh extract them from there?
> 
> 
> I'm all for it.

There is an `obvious' follow on to this.  The target, along with some 
other vectors, could also be put into separate appendicies.

> As a kind of related side effect, what do people think of making the architecture vector table an appendix.  That way it doesn't clutter up the core internals documentation.

What about this?  My guess at what to do next is:

- move the arch vector to the appendix and make it a separate file
- change it to use that weird @defun texi thingie
- add in the missing methods
- finally start worrying about the doco

Andrew

Merge gdbarch.sh and doc/gdbint.texinfo?

[Andrew Cagney]

Hello,

(ok, silly idea of the day)

At present the architecture vector is documented in two places:

- doc/gdbinit.texinfo
- gdbarch.sh

What do people think of moveing gdbarch.sh's table of methods into 
gdbinit.texinfo and have gdbarch.sh extract them from there?

It would, if nothing else, get rid of the `you need documentation' 
problem :-)

As a kind of related side effect, what do people think of making the 
architecture vector table an appendix.  That way it doesn't clutter up 
the core internals documentation.

Andrew