I actually did paste the log in another email, but it said it was being held for the administrator because it was too large of a email. Anyways, I'm going to try to get some more details before i pursue this.
On Sun, 2010-05-30 at 16:46 +0200, Faré wrote: > On 29 May 2010 17:35, Seth Burleigh <[email protected]> wrote: > > OK, so what i usually do when i receive a compile-op error is to simply > > attempt to load the file, which then throws the appropriate error. Maybe > > asdf could do this, when u receive compile-op nil , you can catch the > > error thrown by loading that file? Also, when i attempted to load the > > file in celtk that caused the compile-op nil, no error was thrown, so it > > isn' t a problem with the source code. > > You didn't include a full log of the error, so it's hard to diagnose > what's going on. If it's a regression from ASDF 1, then it's > definitely worth fixing now. Otherwise, I'll just postpone the issue > until after I release ASDF 2. > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] > The Slogan of "Language Independence" is often but the pride that > self-ignorant > monolinguists put in not calling "language" the collection of barkings and > grunts they invent to interact with their computers. — Faré > _______________________________________________ asdf-devel mailing list [email protected] http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
