Probably it was a typo and you meant Plan 9, not Plan B. But anyway, neither Plan B nor the octopus permit / in file names. Most scripts handling file names would break. There was an old discussion about accepting ' ' in file names in this list. I think the same applies, even stronger, here.
On 4/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> d'oh. that's wierd. Is it? You cannot have slashes in filenames, no matter what (that's a decision Plan B should lift by representing, as I believe Rob Pike recommended, paths as arrays of strings rather than slash delimited strings). So what do you expect when fuction names are recorded as filenames in the environment? ++L PS: would it not be even more consistent to use the 'x' bits instead of the 'fn#' prefix to specify which entries in /env are executable?
