Am 10.12.2004 um 08:11 schrieb D. Höhn:
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Peter O'Gorman wrote: | Daniel E. Macks wrote: | |> David R. Morrison <[EMAIL PROTECTED]> said: |> |>> I thus propose to rename the GCC field, calling it GCC-ABI instead. |> |> |> |> Sounds good to me. | | | I don't agree, I agree not to agree with Peter. I do not think that renaming that field is feasable. The advantage gained by adding -ABI is pretty obscure to me. As long as the documentation _clearly_ states what that field is for I could also name it BLUEGIG: and people would know what it stands for. I know that is a drastic example, but I think it illustrates what I mean. As long as the documentation is "bad" no fieldname will save the day.
I gotta side with David H. and Peter in this matter :-). I don't think that we gain anything by renaming the GCC field; but it'll cost us a lot of work to fix up the system for this change. Much better to simply update / clarify the documentation for that field.
Bye,
Max
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
