On Thu, Aug 9, 2012 at 3:01 AM, Markus <li...@neuronenwerk.de> wrote: > Hi Pete, > > my answers became a bit longer than intended. Here's my 5 cent, > but generally, I'd leave the decision to you: > >> Now, this being said, I don't have that much of an issue bumping the >> limit, but 4K seems awfully large for a file path. Would 512 bytes >> be OK with you? > > I'm perfectly ok with that.
You should use PATH_MAX from limits.h period. POSIX says it should be there on *nix and it is also there on windows, being equal to MAX_PATH+1 iirc. Its 4K on linux but its also what the the libc is going to assume so you know you won't run into issues. Hardcoding anything smaller is just asking for issues especially on sample code that people are likely to just Copy/Paste into their projects. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
