Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1 Section 10.1 of the guidelines is not quite accurate

closed-accepted
Otto Wyss
Guidelines (2)
5
2005-04-06
2005-04-05
Grnch
No

It claims that there is no way to find out where the
running executable resides because argv[0] is not
always set to the full path. But, you can easily get
the full path to the running executable by inspecting
the '/proc/self/exe' symbolic link.

Discussion

  • Otto Wyss
    Otto Wyss
    2005-04-06

    • status: open --> open-accepted
     
  • Otto Wyss
    Otto Wyss
    2005-04-06

    Logged In: YES
    user_id=400476

    I agree the wording might not be accurate, so I'll change it
    to "no simple solution".

    Of course it's out of question to add code to read
    '/proc/self/exe' in a cross-platform programming guide.

     
  • Otto Wyss
    Otto Wyss
    2005-04-06

    • assigned_to: nobody --> wyo
    • status: open-accepted --> closed-accepted
     
  • Grnch
    Grnch
    2005-04-06

    Logged In: YES
    user_id=1060442

    Agreed regarding cross-platform, but your examples already
    contain platform-specific code, I saw things like '#ifdef
    __WXMAC__' etc., so I don't think a couple of Linux specific
    lines of code in an #ifdef would be out of place in your
    guidelines, yet they would provide real practical advice to
    anyone facing this issue, instead of "no simple solution".

    In any case, it's no big deal, just a minor nitpick. Good
    work on the guide.