... the hypothetical F" When saying "not valid", I should have said, more precisely, :lib/ is not a valid portable POSIX subdirectory name, because : is not in the portable filenamecharacter set. Specific operating systems and ... the upper and lower case ASCII characters, digits, underscore, period and dash ... ...an extended list of arbitrary single character anchors, it is most concise to...
... Underscore included in the expression of characters to skip for a sensible default...underscore is not a _word_ constituent character? Still, locate-word-at-point could... "_" is a proper character in filenames then why not change the...too literally. But if you want to match any valid file name character, it's simpler to exclude the few invalid characters (NULL, slash, perhaps colon, etc. ...
...the installation directory, and is a validfilename; this would cause much confusion... in URLs to escape unsafe characters, as in %%20 for the ... below). - use a different two-character prefix, preferably one that cannot ... of : would ensure that the filename would not parse under Windows, the character : is in the set of ... which expects a string of filenames. In general, I'm against ...
... (or .\) refers to the current directory (your /wd/), not the installation directory, and is a validfilename; this would cause much confusion. I doubt that this would cause much confusion: This has been... existing practice is equivalent to this proposal). - use a different two-character prefix, preferably one that cannot happen in this position in a ...
...the Forth system can translate the filename with the slashes into the native...naive statement. How does one map filename with slashes into your syntax? ...a superset of the traditional ASCII character set used by versions of OpenVMS.... With extended file specifications, all characters from the 8-bit ISO Latin-1 Multinational character set are valid in file specifications, ...
................ok t/000_standard__pod_coverage....ok t/01_all........................Character in 'C' format wrapped in pack at...lib:/usr/local/src/CPAN/build/File-Filename-1.02-PqdSA3/blib/arch:/usr/local/src/CPAN/build/File-Filename-1.02-PqdSA3/blib/lib:/usr/local...lib:/usr/local/src/CPAN/build/Params-Validate-0.89-VJqUTn/blib/arch:/usr/local/src/CPAN/build/Params-Validate-0.89-VJqUTn/blib/lib:/usr/...
................ok t/000_standard__pod_coverage....ok t/01_all........................Character in 'C' format wrapped in pack at .../lo! cal/src/ CPAN/build/File-Filename-1.02-NJl40z/blib/arch:/usr/local/src/CPAN/build/File-Filename-1.02-NJl40z/blib/lib:/usr/local/...lib:/usr/local/src/CPAN/build/Params-Validate-0.89-CRvtcX/blib/arch:/usr/local/src/CPAN/build/Params-Validate-0.89-CRvtcX/blib/lib:/usr/...
... developers to provide exception handling) is certainly valid, but often you simply do not care...! function result integer :: error_status ! local parameters character(*), parameter :: ROUTINE_NAME = 'myfunc' ! local variables character(256...THEN $ MESSAGE, 'Error reading data from '+Filename, $ /NONAME, /NOPRINT ....etc... END I would ...
... does Swiftforth and VFX Forth apply to Windows filenames in OPEN-FILE, before handing it off to ...the fact that the default separator '%%' is not a validcharacter in file names for Windows. Thanks for that.... Unixen do not offer the same protection for "%%". From his filenames starting with various special characters, sorted in descending order: 1611608 . 6244 %% 1620 # 449 ...
... on that? What processing does Swiftforth and VFX Forth apply to Windows filenames in OPEN-FILE, before handing it off to the system? VFX Forth ... behaviour. This may have something to do with the fact that the default separator '%%' is not a validcharacter in file names for Windows. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, ...
