[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions on EDASM reloc ($FE) files

sicklittlemonkey wrote:

Now we all have access to filenames longer than we can view across
our wide screens, so the naming convention approach is hardly restricted
by namespace.



On Windows, that depends on which directory you're in. ;-)


From WINDEF.H:

#define MAX_PATH          260


Good point.  Since we are all now sensitized to buffer overflow issues,
note that *most* operating systems set a modest limit on total path
length, since they are buffered in so many routines in the OS.

In several places, the ProDOS pathlength limit is 128 bytes.

When a typical file/directory name was a dozen characters, 260 (or 255!)
characters seemed quite generous, but as we become accustomed to names
that push 25-35 characters, or more, and directory structures on 300GB
drives, it's beginning to get a little confining.  ;-)

I note an increasing number of bug reports arising within backup and
synchronization programs which are often asked to copy directories
recursively, getting them into pathlength trouble.

Maybe it's time to start lobbying for a minimum maximum of 1024 bytes...
and at the same time, encourage programmers not to copy pathnames to
local buffers without good reason!

-michael

Music synthesis for 8-bit Apple II's!
Home page:  http://members.aol.com/MJMahon/

"The wastebasket is our most important design
tool--and it is seriously underused."