search for: set_directory

...ctions leave me scratching me head. What purpose does create_file serve? Is there really a need to create empty files? (It also leaks an open file handle, BTW). I would expect set_file to alter only the file name portion of the path and leave the directory portion unchanged, and the opposite for set_directory. set_directory obliterates the file name portion of the path (OK, I guess) but set_file doesn't make any sense at all. -------------- next part -------------- A non-text attachment was scrubbed... Name: Path.diff Type: application/octet-stream Size: 10799 bytes Desc: not available URL: <htt...

Jeff, Your patch has been committed. Thanks! Reid. Jeff Cohen wrote: > Alas, you missed a serious bug in that same function. Patch attached to > fix it and improve some comments. No more late night coding for me :) > > That leaves Path.cpp. Once that's done I can actually try and execute > this stuff. > > > On Thu, 16 Sep 2004 08:55:28 -0700 > Reid Spencer

Alas, you missed a serious bug in that same function. Patch attached to fix it and improve some comments. No more late night coding for me :) That leaves Path.cpp. Once that's done I can actually try and execute this stuff. On Thu, 16 Sep 2004 08:55:28 -0700 Reid Spencer <reid at x10sys.com> wrote: > This version has been committed to CVS with one minor change: > I made the

...tching me head. What purpose > does create_file serve? Is there really a need to create empty files? > (It also leaks an open file handle, BTW). I would expect set_file to > alter only the file name portion of the path and leave the directory > portion unchanged, and the opposite for set_directory. set_directory > obliterates the file name portion of the path (OK, I guess) but set_file > doesn't make any sense at all. > > ______________________________________________________________________ > _______________________________________________ > LLVM Developers mailing l...

...j/lib/Debug/libLLVMsystem.a(Path.o): In function `llvm::sys::Path::Path(std::string)': > /usr/home/llvm/obj/lib/System/platform/Path.cpp:32: undefined reference to `llvm::sys::Path::is_valid() const' > /usr/home/llvm/obj/lib/Debug/libLLVMsystem.a(Path.o): In function `llvm::sys::Path::set_directory(std::string const&)': > /usr/home/llvm/obj/lib/System/platform/Path.cpp:131: undefined reference to `llvm::sys::Path::is_valid() const' > /usr/home/llvm/obj/lib/Debug/libLLVMsystem.a(Path.o):/usr/home/llvm/obj/lib/System/platform/Path.cpp:148: more undefined references to `llvm::s...

Reid, >As for Interix support in general, I'm having a hard time determining >which variant of Unix Interix implements. It seems to be partially Posix >1 and partially Posix 2 based. Do you have any further information >related to the specific standards supported by Interix? I don't want to >incorrectly categorize the Interix support. I've discussed this subject with

Jeff/Vladimir: As with Interix, I've recently added support for FreeBSD into lib/System. Currently, the implementation of FreeBSD just uses the "generic Unix" implementation which probably should work on FreeBSD. If not, I would appreciate it if you could make patches in the FreeBSD directory. If you do, don't forget that you need to remove anything that doesn't work in the

...eDialog#get_paths":#FileDialog_getpaths </span><del>-* "FileDialog#get_style":#FileDialog_getstyle </del><span class="cx"> * "FileDialog#get_wildcard":#FileDialog_getwildcard </span><span class="cx"> * "FileDialog#set_directory":#FileDialog_setdirectory </span><span class="cx"> * "FileDialog#set_filename":#FileDialog_setfilename </span><span class="cx"> * "FileDialog#set_filter_index":#FileDialog_setfilterindex </span><span class="cx"&...

en fait je vous renvoi ce message car maintenant la taille de la police change au bout de 500 lignes environ, alors que j''avais reussi à garder la taille jusqu''à environ 5000 lignes. Je ne comprend pas. Est-ce que c''est instable? le bout de code que vous m''avez envoyer ne marche pas. merci Sebastien _______________________________________________ wxruby-users

I''m trying to run puppetmasterd the first time with --mkusers. It fails with the following error message: 001 # /usr/bin/puppetmasterd --mkusers Could not configure for running; got 1 failure(s) Adding --verbose and --debug does nothing to improve the output. How do I begin to debug this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are