From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <012f01c0c6b0$0bfba9c0$e0b6c6d4@SOMA> From: "Boyd Roberts" To: <9fans@cse.psu.edu> References: <20010416184538.3F48719A0A@mail.cse.psu.edu> Subject: Re: [9fans] Spaces in values in plan9.ini? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Date: Mon, 16 Apr 2001 22:01:37 +0200 Topicbox-Message-UUID: 827d437c-eac9-11e9-9e20-41e7f4b1d025 From: "rob pike" > That sort of thing was precisely the reason for the change > to tokenize. Please try it, see if it works, and tell us the > result. Thanks. yeah, a long while i had to write a DLL that looked like WinSock 1.1 and then called winsock to talk SOCKS 4 transparently; so no need for proxy configs. it had a 'routing' table to find socks servers, but then it needed an .ini file. is it GetProfileString() and all that crap that reads those things (it's been a while)? anyway, even though it was only read once, i was told to re-write the code so the DLL would start more quickly. trouble was, the .ini files were not _really_ documented so i just had to make it up as i went along. all sorts of horrible sections, white space, quoting etc... i woulda stuck with GetProfileDebacle() 'cos at least it knew the format, but i was a contractor and was told to break it. one of the reasons for the .ini file IIRC was that you could up read/write buffer sizes to > 16kb [windows 3] and at that point netscape would crash, so the .ini file specfied in what chunks to splits 'large' i/o's up into -- puke. nasty. i needed a job here, they forced me to code on windows 3, '95 and NT. ain't CreateProcess() a beauty? thanks Dave Cutler. -- Boyd Roberts http://www.insultant.net boyd@insultant.net Rule 1: Whenever there is any doubt, there is no doubt. Rule 2: I don't remember. Rule 3: Take the hit and drive on.