"Pascal J. Bourguignon" <[email protected]> writes: > The problem is that CL:DIRECTORY is specified to apply TRUENAME which is > specified to resolve symbolic links. (See section 20.1.3 Truenames). > > There is no conforming way to obtain the pathname of a symbolic link in > CL. You have to use an extension, either an implementation specific > keyword argument to DIRECTORY, or an implementation specific function.
I don't mind using implementation-specific functionality. > On POSIX systems, I'd advise to use the POSIX API thru CFFI to deal with > the POSIX file systems. I don't consider this a viable option right now. Zach ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Ecls-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecls-list
