forked from synesissoftware/recls
-
Notifications
You must be signed in to change notification settings - Fork 0
/
FAQ.txt
100 lines (71 loc) · 4.4 KB
/
FAQ.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
============================================================================
recls - FAQ
-----------
; Created: 28th May 2006
; Updated: 11th August 2009
============================================================================
The recls FAQ is below. Post new questions on the STLSoft newsgroup
(news://news.digitalmars.com/c++.stlsoft/). Please prefix your post with
"[recls] ".
10. Is there a newsgroup for recls?
No, but users have tended to post to the STLSoft newsgroups, which is
kindly provided by Digital Mars.
9. Is there a documentation/tutorial besides the API documentation?
Well, yes and no. Almost all of the developments in the core library and
the mappings have been documented in my column Positive Integration in
C/C++ Users Journal (available online at www.ddj.com/columns/wilson). If
you're a subscriber to either CUJ or to DDJ's online resources, then you
can read all about them there.
In addition, there are very plainly written (at least that's the
intention) examples in C and C++, and all of the mapped languages, which
demonstrate most/all the available functionality.
But I'm always painfully aware that my documentation is lacking, so if
there're specific ideas you have for improving it, please let me know, and
I'll be happy to tackle them.
8. Why should I lash out US$40 of my hard-earned cash for your book
Imperfect C++? I mean, I know it's currently packing five stars on
Amazon.com, but what does it give me?
H.J., that's a great question. All I can say is that if you're a
practising C++ programmer, who is interested in any/all of the issues of
portability, robustness, efficiency or maintainability, then Imperfect C++
is the book for you! And that's my honest, unbiased opinion. :-)
7. The D standard library docs for recls do not correspond to the version
included with the D compiler. What gives?
Since version 1.2.1 of recls, Walter Bright, the creator of D, has not
accepted any updates to recls due to concerns over its code size, both
source and object. Naturally, this has caused consternation for some D
users, who've had to manually compile/build/link std.recls from the
libraries available on this site. Thankfully, version 1.6.1 of recls
includes significant work to refactor the implementation, and trim it
down, and I expect 1.6.1 of recls to feature in the D standard library in
March 2005.
6. Does recls support breadth-first searching (BFS)?
Not at the moment. However, after version 1.6.1, I plan to fork the
library and produce recls 2.0, which will introduce substantial changes,
including filtering on size/date/attributes, plug-in pattern matching,
other recursive system searches (such as Win32 registry, CVS, etc.), and
BFS. I expect this will be out sometime mid 2005.
5. Why do you use your own STLSoft libraries? Why not use Boost?
Since I wrote STLSoft, I am very familiar with the facilities the
libraries provide, and am able to best use them. I have also added new
components to STLSoft as a result of the requirements of recls, which I
would not be able to do so easily for another library, such as Boost.
4. When will recls support FTP enumeration?
As of version 1.5.1 (available from 10th June 2004), recls supports FTP
enumeration for Win32. Support for UNIX will be included in a forthcoming
release.
3. Can anyone contribute to recls?
Certainly.
2. I'm developing an application that needs to run on both WinTEL and Linux, and I'd like to use recls. When will recls support UNIX?
Version 1.2.1 (available from 23rd January 2004) supports Linux. Although
it's not been tested on other UNIX flavours it uses no Linux-specific
features, and is very likely to port without any problems to them. All
they need is the readdir(), glob() and stat() APIs
1. How is this different from ls, which is recursive as well?
The idea is to have a platform-independent recursive search library, which
can be used in any application, rather than a platform-specific recursive
searching utility, such as ls. By providing mappings to a whole host of
different languages, the kind of code that most people have knocked up for
recursive searching in C or C++ will now be available to developers in
almost any language, and in a well-tested and highly portable form.
=============================== End of file ================================