whitespace and comment refactoring
This patch replaces tabs with spaces and converts the '%' inline comments (which according to the emacs mode are actually end of line comments) to the mode acceptable '%%' inline comments. Signed-off-by: Jordan Wilberding <diginux@gmail.com>
This commit is contained in:
parent
960548301e
commit
8353035a1e
7 changed files with 182 additions and 182 deletions
|
@ -123,10 +123,10 @@ mkdtemp() ->
|
||||||
%% @doc Makes a directory including parent dirs if they are missing.
|
%% @doc Makes a directory including parent dirs if they are missing.
|
||||||
-spec mkdir_path(path()) -> ok.
|
-spec mkdir_path(path()) -> ok.
|
||||||
mkdir_path(Path) ->
|
mkdir_path(Path) ->
|
||||||
% We are exploiting a feature of ensuredir that that creates all
|
%% We are exploiting a feature of ensuredir that that creates all
|
||||||
% directories up to the last element in the filename, then ignores
|
%% directories up to the last element in the filename, then ignores
|
||||||
% that last element. This way we ensure that the dir is created
|
%% that last element. This way we ensure that the dir is created
|
||||||
% and not have any worries about path names
|
%% and not have any worries about path names
|
||||||
DirName = filename:join([filename:absname(Path), "tmp"]),
|
DirName = filename:join([filename:absname(Path), "tmp"]),
|
||||||
try
|
try
|
||||||
ok = filelib:ensure_dir(DirName)
|
ok = filelib:ensure_dir(DirName)
|
||||||
|
@ -343,7 +343,7 @@ setup_base_and_target() ->
|
||||||
{BaseDir, SourceDir, {Name1, Name2, Name3, NoName}}.
|
{BaseDir, SourceDir, {Name1, Name2, Name3, NoName}}.
|
||||||
|
|
||||||
find_test() ->
|
find_test() ->
|
||||||
% Create a directory in /tmp for the test. Clean everything afterwards
|
%% Create a directory in /tmp for the test. Clean everything afterwards
|
||||||
|
|
||||||
{setup,
|
{setup,
|
||||||
fun setup_base_and_target/0,
|
fun setup_base_and_target/0,
|
||||||
|
|
|
@ -111,9 +111,9 @@ map_gather([{Pid, _E} | Rest]) ->
|
||||||
receive
|
receive
|
||||||
{Pid, {value, Ret}} ->
|
{Pid, {value, Ret}} ->
|
||||||
[Ret|map_gather(Rest)];
|
[Ret|map_gather(Rest)];
|
||||||
% timeouts fall here too. Should timeouts be a return value
|
%% timeouts fall here too. Should timeouts be a return value
|
||||||
% or an exception? I lean toward return value, but the code
|
%% or an exception? I lean toward return value, but the code
|
||||||
% is easier with the exception. Thoughts?
|
%% is easier with the exception. Thoughts?
|
||||||
{Pid, Exception} ->
|
{Pid, Exception} ->
|
||||||
killall(Rest),
|
killall(Rest),
|
||||||
throw(Exception)
|
throw(Exception)
|
||||||
|
@ -153,9 +153,9 @@ do_f(Parent, F, E) ->
|
||||||
Parent ! {self(), {value, Result}}
|
Parent ! {self(), {value, Result}}
|
||||||
catch
|
catch
|
||||||
_Class:Exception ->
|
_Class:Exception ->
|
||||||
% Losing class info here, but since throw does not accept
|
%% Losing class info here, but since throw does not accept
|
||||||
% that arg anyhow and forces a class of throw it does not
|
%% that arg anyhow and forces a class of throw it does not
|
||||||
% matter.
|
%% matter.
|
||||||
Parent ! {self(), Exception}
|
Parent ! {self(), Exception}
|
||||||
end.
|
end.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue