It's not hard to automatically copy-the .rel to a .o file for those rare
times it actually is needed.
I believe you will find the choice of .o is related to the 'traditional'
naming of files created by the earliest Z80 assemblers and compilers on
both dedicated OS's and CP/M.

Art

----Original Message-----
From: Borut Razem <borut.ra...@siol.net>
Reply-To: sdcc-user@lists.sourceforge.net
To: Sdcc-Devel <sdcc-de...@lists.sourceforge.net>, Sdcc-User
<sdcc-user@lists.sourceforge.net>
Subject: [Sdcc-user] Object file extension for Z80 and gb
Date: Sat, 09 Jan 2010 18:07:53 +0100

The z80 and gb targets object file has been changed from .o to .rel.

Borut


Borut Razem wrote:
> Hello sdcc developers and users,
>
> I'm thinking about changing the object file exetnsion for z80 and gb 
> targets from .o to .rel, which is used by all other targets. The 
> original asxxxx also uses .rel extensin for z80 an gb. I don't know 
> why it was changed from .rel to .o. I think it is a heritage from the 
> Gameboy Development Kit project. Probably Michael Hope can give us an 
> explanation.
>
> The reason of the proposed change is unification and re-merge with the 
> latest asxxxx version.
>
> I know that the change introduce backward compatibility problems, but 
> the next sdcc release will be "major" release: the major release 
> number will be changer from 2 to 3 (2.9 to 3.0), so maybe we can even 
> afford some backward incompatibilities...
>
> I expectation of your opinions,
> Borut
>





------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to