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

search-path entries are truncated to NAME_LEN #55

Open
pipcet opened this issue May 14, 2017 · 2 comments
Open

search-path entries are truncated to NAME_LEN #55

pipcet opened this issue May 14, 2017 · 2 comments
Labels

Comments

@pipcet
Copy link
Contributor

pipcet commented May 14, 2017

lbForth$ strace -e open ./b-forth
[...]
s" /this/is/a/really/really/long/path" searched
 ok
include foo.fth
open("/this/is/a/realfoo.fth", O_RDONLY) = -1 ENOENT (No such file or directory)
@larsbrinkhoff
Copy link
Owner

As you probably know, this is because path strings are stored as word names in the dictionary.

This isn't much of a issue for the C target per se, because it's not intended for serious use. Except it's also used to bootstrap a "real" target, which may be a problem.

So for me, it boils down to: does bootstrapping necessarily involve searching long paths? I don't think so.

@larsbrinkhoff
Copy link
Owner

Names are also truncated in other targets. Notably the x86 target.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants