[task #15755] Citing CPU architecture in a macro in the project

[Mohammadreza Khellat]

Follow-up Comment #3, task #15755 (project reproduce):

Thanks Mohammad for the corrections :)

Yeah, regarding filename limitations, at first I wanted to rule out the 20-22
unix shell special characters. But then I said to myself, maybe we can come up
with a simpler convention by only allowing :alnum:, -, and /.

Anyways, the discussion around "filenames" is related to the filesystem
specifications (specifically limitations) as well as shell internals _when
filenames are not stores as strings_. 

Just as a reference:
https://en.wikipedia.org/wiki/Comparison_of_file_systems
[apart from / and NUL, there are no limitations for ext2+ and btrfs. As for
xfs and hpfs the only limitation is NUL].

Regarding shell special characters when filename is not stored as string, I
think we should add the following characters to the list in the 'case' in
Commit c6a4aaad62a9
<http://git.maneage.org/project.git/commit/?id=c6a4aaad62a9>:
* ~ 
* | 
* `  (archaic)
* [ , ]
* ' , "
* < , >

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15755>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/