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
Add a 'target' field for symlinkattributes #76
Conversation
* Make lfs export luaopen_lfs under Windows
It returns the resolved path of the symlink.
|
(I don't know why these other commits 6e0dc7b and 7dae11c ended up in this PR too, but I guess they should be in |
| */ | ||
| static int push_link_target(lua_State *L) { | ||
| #ifdef _WIN32 | ||
| errno = ENOSYS; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not implement on windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be my guest! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So that implies it was just a lack of time rather than a technical obstacle?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and interest — I usually don't do Windows coding for free :)
|
For cross-referencing: I noticed that this closes #43. |
Probably because I haven't merged |
|
Not sure what is going on with LuaJIT failures, see mpeterv/hererocks#27. |
|
@hishamhm I don't like that to getting size for |
|
Alternatively, it should be possible to use existing mechanism for declaring functions pushing fields. But then there has to be a way to use different field lists for |
|
I'd like to suggest a different approach for determining the buffer size: Start with a reasonable initial value (say 256 or 512), and check the If you wish, I'll create a pull request for this. [EDIT] P.S.: I realized that |
|
@n1tehawk yes, this PR would be welcome! |
|
See #78. Compared to my previous suggestion, I have added proper Regards, NiteHawk |
|
This PR was superseded by merging #78, and should be closed. Regards, NiteHawk |
It returns the resolved path of the symlink.
Since this adds functionality, this should be merged in the 1.7 branch. PRing for review.