Tim X <firstname.lastname@example.org> wrote:
| For me, the most difficult part of starting to use CL was actually
| finding the functions which you knew had to exist, but couldn't find
| because you didn't know what they were called.
I think we've all experienced at least some of that. For example,
consider the ubiquitous Unix "basename" program & library function.
I knew about PATHNAME-NAME a long time ago (relatively speaking),
but it doesn't do that job if you have periods in the filename,
of course, you have to take the outputs from both PATHNAME-NAME
and PATHNAME-TYPE and then munge them back together [which might
not always even work if the original filename had *mutliple* periods
in it], so I'd been coding up my own idiosyncratic BASENAME routine
over & over again. I only *very* recently found out that CL also
has FILE-NAMESTRING, which does pretty much "the right thing"
as a "basename" replacement!
I now also know that DIRECTORY-NAMESTRING exists, and is
sometimes what I really need instead of PATHNAME-DIRECTORY.
| Once I know the name, I often look it up in the hyperspec as
| this provides really useful and concise information.
The CLHS's "Permuted Symbol Index" [bottom half of
can really come in handy here. If you've got even *part* of the
name right, you can usually find the right thing in the permuted
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607