HPPA files naming convention...

HPPA files naming convention...

[Joel Brobecker]

I find the naming convention for the hppa targets too short for my
liking: - hppah  -> hppa on hpux
        - hppao  -> hppa on osf
        - hppab  -> hppa on bsd

I suggest we transition to a more verbose naming, which should be more
consistent with the other ports I know. For instance, how about
hppa-hpux instead of hppah. I hear a netbsd port will probably be done
in the future, we can then use hppa-netbsd.

We would use this convention for the files in the config/pa directory
(tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
(hppa-hpux-tdep.c).

The part that is indenpedent of the OS would still stay in hppa (eg
tm-hppa, hppa-tdep.c, etc).

Does this seam like a good idea?
-- 
Joel

Re: HPPA files naming convention...

[Daniel Jacobowitz]

On Mon, Nov 25, 2002 at 04:56:31PM -0800, Joel Brobecker wrote:
> I find the naming convention for the hppa targets too short for my
> liking: - hppah  -> hppa on hpux
>         - hppao  -> hppa on osf
>         - hppab  -> hppa on bsd
> 
> I suggest we transition to a more verbose naming, which should be more
> consistent with the other ports I know. For instance, how about
> hppa-hpux instead of hppah. I hear a netbsd port will probably be done
> in the future, we can then use hppa-netbsd.
> 
> We would use this convention for the files in the config/pa directory
> (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
> (hppa-hpux-tdep.c).
> 
> The part that is indenpedent of the OS would still stay in hppa (eg
> tm-hppa, hppa-tdep.c, etc).
> 
> Does this seam like a good idea?

Absolutely!  My tab completion loves you!

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: HPPA files naming convention...

[Jason R Thorpe]

On Mon, Nov 25, 2002 at 04:56:31PM -0800, Joel Brobecker wrote:

 > I find the naming convention for the hppa targets too short for my
 > liking: - hppah  -> hppa on hpux
 >         - hppao  -> hppa on osf
 >         - hppab  -> hppa on bsd
 > 
 > I suggest we transition to a more verbose naming, which should be more
 > consistent with the other ports I know. For instance, how about
 > hppa-hpux instead of hppah. I hear a netbsd port will probably be done
 > in the future, we can then use hppa-netbsd.
 > 
 > We would use this convention for the files in the config/pa directory
 > (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
 > (hppa-hpux-tdep.c).

The convention sort of varies based on OS ... NetBSD platforms use e.g.
alphanbsd-tdep.c vs. the Linux alpha-linux-tdep.c.  .mt and .mh files
for NetBSD in the processor-specific directory are usually just called
e.g. alpha/nbsd.mh.

So, for your configurations, select whatever convention suits you.  But
be prepared for other OS config conventions to creep into the mix at
some point :-)

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>

Re: HPPA files naming convention...

[Eli Zaretskii]

On Mon, 25 Nov 2002, Joel Brobecker wrote:

> I suggest we transition to a more verbose naming, which should be more
> consistent with the other ports I know. For instance, how about
> hppa-hpux instead of hppah. I hear a netbsd port will probably be done
> in the future, we can then use hppa-netbsd.
> 
> We would use this convention for the files in the config/pa directory
> (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
> (hppa-hpux-tdep.c).
> 
> The part that is indenpedent of the OS would still stay in hppa (eg
> tm-hppa, hppa-tdep.c, etc).

Just remember to update gdb/config/djgpp/fnchange.lst.

Re: HPPA files naming convention...

[Andrew Cagney]

> I find the naming convention for the hppa targets too short for my
> liking: - hppah  -> hppa on hpux
>         - hppao  -> hppa on osf
>         - hppab  -> hppa on bsd

What about the other way.

panbsd-tdep.c
pa-linux-tdep.c
pa-hpux-nat.c

for reasons unknown gdb ended up with config/pa instead of config/hppa.

> I suggest we transition to a more verbose naming, which should be more
> consistent with the other ports I know. For instance, how about
> hppa-hpux instead of hppah. I hear a netbsd port will probably be done
> in the future, we can then use hppa-netbsd.
> 
> We would use this convention for the files in the config/pa directory
> (tm-hppa-hpux.h, hppa-hpux.mt, etc), and also for for the files in gdb
> (hppa-hpux-tdep.c).
> 
> The part that is indenpedent of the OS would still stay in hppa (eg
> tm-hppa, hppa-tdep.c, etc).
> 
> Does this seam like a good idea?

but which ever.  (To follow up eli's comment, watch the ari for name 
space problems).

Andrew