Thanks Larry. I had always been under the impression that forward slashes weren't acceptable in Windows path names so I'm glad to hear they are. The project I'm working on has to run on Macs as well as Windows and the forward slash is acceptable on both platforms. Pete
On Tue, Jan 31, 2012 at 9:00 AM, <sqlite-users-requ...@sqlite.org> wrote: > Message: 16 > Date: Mon, 30 Jan 2012 21:12:59 -0800 > From: Larry Brasfield <larry_brasfi...@iinet.com> > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] sqlite3 question > Message-ID: <4f27785b.7030...@iinet.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > If you look at shell.c in the code implementing > sqlite3.exe, you will find a procedure named > resolve_backslashes(char *z) which performs a > substitution of '\'-escaped characters that is > similar to the C/C++ interpretation of string > literals. That is what has sucked up those > backslashes. > > Getting to what you should do: I advise using > plain '/' as the path separator, unless you are > fond of using '\\'. The OS is perfectly willing > to accept '/'. (I curse IBM's insistence that > the backwards convention started in CPM had to > be prolonged into MS-DOS. There are fewer and > fewer contexts where programs are silly enough > to insist on seeing '\' rather than the '/' the > rest of the world has settled upon. > > Cheers, > -- > Larry Brasfield > -- Pete Molly's Revenge <http://www.mollysrevenge.com> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
