3 ms·
What's wrong with the C version? char *dir = "/foo"; mkdir(dir, 0700); if (chdir(dir) == 0) delete_all_files();
by tedunangst 12y ago
What's wrong with the C version?
char *dir = "/foo";
mkdir(dir, 0700);
if (chdir(dir) == 0)
delete_all_files();
- swah 12y agoNothing, of course. I just find the macros that give you a "modified environment" to run some code short and sweet. with-temp-buffer is another example: a macro that bridges the functions for "string manipulation" and the ones for "buffer manipulation", since you start writing stuff this way: (defun replace-in-string (str from to) (with-temp-buffer (insert str) (beginning-of-file) ;;; Here you can use all your normal text editing commands (replace-regexp from to nil t) (buffer-string))) Lots of dirty manipulation, but from outside its a pure function, and doesn't change the editor state in any way after it runs.
- qewrffewqwfqew 12y agoThat's incomplete in that it doesn't automatically chdir back. A proper block-scope "with-" macro will wrap the body in something like: char *olddir = getcwd(); chdir(newdir); try { do_stuff(); } finally { chdir(olddir); }
- jacquesm 12y ago'try' and 'finally' are in C now? Someone should warn the GCC guys they're behind the times. Also, getcwd has a size parameter these days, and of course you want to check if the getcwd actually worked.
- xxs 12y agoThe OP said: wrap in a macro having similar properties (ala pseudo code).
- jacquesm 12y agoGood luck writing a macro in C to express language functionality for which you don't have the primitives. It's not exactly lisp. Think of C macros as a way to save you some typing and lisp macros as a way to extend the language.
- xxs 12y agoyou can definitely save the chdir and restore it macro.
- tedunangst 12y agosetjmp and longjmp are sufficient building blocks for this.
- xxs 12y agoAny multithreaded code will be destroyed if relying on chdir. chdir should be deprecated, as resolving relative to is just trivial in an application.