Ciaran McCreesh wrote:
Nor do most Unix apps, since they tend to be written in C using all
those C library functions that work on null terminated strings.
Null introduces far more problems than it solves, character-wise...
..but it's fine as a terminator, if you know what you're doing.
On Thu, Apr 17, 2008 at 6:31 AM, Duncan [EMAIL PROTECTED] wrote:
While you are almost certainly correct on POSIX/Unix filenames and the
shell won't accept / in a filename, IIRC (from reading) it's often
possible for C programs to code a literal / in a filename, and possible
for some
Rémi Cardona [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Thu, 17 Apr 2008 07:49:23 +0200:
Duncan a écrit :
Whatever your faults, you /do/
tend to be quite accurate on such things.
Wow, you've managed to turn a nice technical discussion (which is rare
enough in recent
Santiago M. Mola [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted
below, on Thu, 17 Apr 2008 11:51:32 +0200:
If that's possible, we shouldn't support it anyway. If someone wants to
use /var/tmp/port\/age we'll just stab him, if someone releases a
tarball with such filenames we'll stab
Ciaran McCreesh [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted below, on Wed, 16 Apr 2008
18:24:05 +0100:
On Wed, 16 Apr 2008 19:17:51 +0200
Frank Gruellich [EMAIL PROTECTED] wrote:
I was not able to create a filename or path containing it. (Anyone
else?)
Unix file names can't
Duncan a écrit :
Whatever your faults, you /do/
tend to be quite accurate on such things.
Wow, you've managed to turn a nice technical discussion (which is rare
enough in recent history) into a let's-start-bashing-people thread.
You've lost all credibility in just one sentence... Pity.
If
