[golang-dev] code review 6736069: runtime, syscall, os: add os.ExecPath() (string, error) (issue 6736069)

[golang-dev] code review 6736069: runtime, syscall, os: add os.ExecPath() (string, error) (issue 6736069)

	Minux Ma
	Oct 28, 2012 at 3:43 pm

On 2012/10/26 16:36:37, r wrote:
is your name minuxName?

good point. PTAL.

btw, how to implement this on Plan 9?

https://codereview.appspot.com/6736069/

Search Discussions

Follow ups

Rob Pike: The file names are inappropriate now. For Plan 9, it depends what you want this for. /proc/PID/text is always a working name for the executable. Otherwise I don't know if it's possible. -rob
Minux Ma: do you have suggestions for the filenames? i think executable is a bit too long, and exec might confuse with the exec syscall. how about the original execpath? I've thought about /proc/PID/text, in fact it can pass the test, but i think the main use of this to determine the original binary's path so that the binary can access its bundled asset files, for example. i'd also like to test we can indeed find the other files around the binary, but given the current go test's behavior, this is
Minux Ma: PTAL. Patch Set 24 is the same as Patch Set 23 except s/progpath/executable/ in filenames. https://codereview.appspot.com/6736069/

Discussion Navigation

view	thread \| post
posts	‹ prev \| 26 of 58 \| next ›

Discussion Overview

font	variable	Hotkey: f
user style	avatars	Hotkey: a