Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop using the flag library #15

Closed
fzerorubigd opened this issue Sep 8, 2015 · 0 comments · Fixed by #16
Closed

Stop using the flag library #15

fzerorubigd opened this issue Sep 8, 2015 · 0 comments · Fixed by #16

Comments

@fzerorubigd
Copy link
Contributor

The standard flag library is not a part of Go that everyone love and use. Personally I (and many other) like another flag library.
The problem is, with this library, we should use the standard flag library (LAME IMHO), or else, this won't work.
I think, using the flag library is not required at all, since the parent process, can simply change env for the child library.

And the other problem is, I want to change it to system fork (not execute with os.exec) and in that case I can not use the flag library, since the child is exactly like parent and there is no way to change child Arguments.

fzerorubigd added a commit to fzerorubigd/endless that referenced this issue Sep 8, 2015
fzerorubigd added a commit to fzerorubigd/endless that referenced this issue Sep 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant