[Bug 59703] Changed - No way of error detection for g_get_current_dir()

["Timur I. Bakeyev" <mc listserv bat ru>]

Hi, Pavel!

Here is what I got from Owen.. I guess, we should follow advice, and
bring our own mc_current_wd() (or what was the name?) back....


With regards,
	    Timur.


----- Forwarded message from bugzilla-daemon widget gnome org -----

Date: Wed, 19 Sep 2001 11:08:26 -0400 (EDT)
From: bugzilla-daemon widget gnome org
Subject: [Bug 59703] Changed - No way of error detection for g_get_current_dir()
To: gtkdev gtk org, timur gnome org ru
Cc: 

http://bugzilla.gnome.org/show_bug.cgi?id=59703

*** shadow/59703	Sat Sep  8 07:50:04 2001
--- shadow/59703.tmp.22700	Wed Sep 19 11:08:26 2001
***************
*** 3,10 ****
  Version: 1.3.x
  OS: All
  OS Details: 
! Status: NEW   
! Resolution: 
  Severity: major
  Priority: Normal
  Component: general
--- 3,10 ----
  Version: 1.3.x
  OS: All
  OS Details: 
! Status: RESOLVED   
! Resolution: WONTFIX
  Severity: major
  Priority: Normal
  Component: general
***************
*** 36,38 ****
--- 36,52 ----
  all the programms, that rely on this broken behaviour should be reviewed. If we leave this behaviour now, it'll become a part of API, and we never get rid of it....
  
  I guess, glib2.0 should be examed agains such ill-behaved functions NOW.  I'm afraid, that there are more of them than only this one...
+ 
+ ------- Additional Comments From otaylor redhat com  2001-09-19 11:08 -------
+ We can't change this function; most users of this function
+ would be _more_ broken if it suddenlty started returning
+ NULL than currently. Nobody would know to test for NULL,
+ so they would segfault. 
+ 
+ Yes, returning "/" when an error occurs is bad, I won't
+ defend it, but basically when getcwd() is erroring things 
+ are going to be pretty screwed up anyways, and studying 
+ most code using g_get_current_dir(), it would be pretty 
+ difficult to do much better.
+ 
+ I would advising writing your own utility function for mc

----- End forwarded message -----