http://www.riscos.info/bugzilla3/show_bug.cgi?id=179

           Summary: Inconsistent handling of HOME in UnixLib
           Product: GCC/GCCSDK
           Version: other
          Platform: Other
        OS/Version: RISC OS
            Status: NEW
          Severity: feature request
          Priority: P1
         Component: Unixlib and SharedCLibrary
        AssignedTo: [email protected]
        ReportedBy: [email protected]
   Estimated Hours: 0.0


Current behaviour is approximately:

If HOME environment var is set, use that.  This is mostly set by !UnixHome, and
is in a unix format.  

If not set, use Choice$Write.  This is usually a RISC OS path variable in RISC
OS format.  

The code for this is in __pwddefault in pwdread.c, and this should be the only
handling of the value, no matter what it is.

Probably we want to deprecate use of !UnixHome, it has outlived its usefulness
- in most cases we really want to use Choices:, etc.  For many games, we do in
fact use "/<Choices$Write>/" explicitly as a unix filename representation of
the RISC OS path.  We also tend to remove the leading "." use for unix-style
choices - more like the setup in Windows.

Problems:

- unix/glob.c and common/riscosify.c both use getenv("HOME") - they should use
the central logic.

- The Choices$Write value ought to be unixified. 

- We ought to deprecate !UnixHome.  One work around here would to be
immediately use Choices$Write, and only fall back to HOME just in case.

- Finally, we might consider in riscosify trimming any leading "." value as
part of a filename in Choices$Write.

Some of these changes might have other consequences, so please express any
concerns.

-- 
Configure bugmail: http://www.riscos.info/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Reply via email to