[Ecls-list] understand ECL source code

tommaso.tagliapietra at essellesse.net tommaso.tagliapietra at essellesse.net
Fri Jan 9 00:56:05 UTC 2004


Something can tell me where can I find documentations usefull to understand
ECL  C source code?? I must to understand how it work and it's architecture.

thnx,
    Tommy

----- Original Message -----
From: <ecls-list-request at lists.sourceforge.net>
To: <ecls-list at lists.sourceforge.net>
Sent: Friday, January 09, 2004 5:00 AM
Subject: Ecls-list digest, Vol 1 #222 - 4 msgs


> Send Ecls-list mailing list submissions to
> ecls-list at lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/ecls-list
> or, via email, send a message with subject or body 'help' to
> ecls-list-request at lists.sourceforge.net
>
> You can reach the person managing the list at
> ecls-list-admin at lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ecls-list digest..."
>
>
> Today's Topics:
>
>    1. Re: Xmas fixes (Marco Antoniotti)
>    2. Re: Xmas fixes (Juan Jose Garcia-Ripoll)
>    3. Re: Xmas fixes (Marco Antoniotti)
>    4. red hat linux 9 cvs build failure (Dennis)
>
> --__--__--
>
> Message: 1
> Date: Thu, 8 Jan 2004 11:42:26 -0500
> Subject: Re: [Ecls-list] Xmas fixes
> From: Marco Antoniotti <marcoxa at cs.nyu.edu>
> To: ecls-list at lists.sourceforge.net
>
>
> On Thursday, Jan 8, 2004, at 06:24 America/New_York, Juan Jose
> Garcia-Ripoll wrote:
>
> > Finally the Xmas were more distracting than I hoped, and some issues
> > raised
> > about pathnames made me forget some more appealing projects. These are
> > the
> > changes to ECL after these weeks (available in CVS):
> >
> > + Fixes in the routines that deal with pathnames and access the
> > filesystem:
> > they now merge all pathnames with *DEFAULT-PATHNAME-DEFAULTS* and thus
> > it is
> > possible to use this variable as a sort of lisp current working
> > directory.
> >
> > + New function SI::GETCWD returns the current working directory of the
> > C
> > library.
>
> Is this exported or not?  Doe it return a pathname?
>
>
>
> >
> > + SI::CHDIR now takes a boolean as a second argument:
> > (SI::CHDIR new-directory &optional update-d-p-d)
> > If update-d-p-d is true, then *DEFAULT-PATHNAME-DEFAULTS* takes is set
> > to the
> > truename of the new working directory.
>
> Same here.  Is it exported?
>
> Cheers
>
> --
> Marco Antoniotti http://bioinformatics.nyu.edu
> NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488
> 715 Broadway 10th FL fax. +1 - 212 - 998 3484
> New York, NY, 10003, U.S.A.
>
>
>
> --__--__--
>
> Message: 2
> From: Juan Jose Garcia-Ripoll <worm at arrakis.es>
> To: ecls-list at lists.sourceforge.net
> Subject: Re: [Ecls-list] Xmas fixes
> Date: Thu, 8 Jan 2004 18:18:32 +0100
>
> On Thursday 08 January 2004 17:42, Marco Antoniotti wrote:
> > > + New function SI::GETCWD returns the current working directory of the
> > > C
> > > library.
> >
> > Is this exported or not?  Doe it return a pathname?
>
> Yes, it is exported from the SYSTEM (or SI) package and it always returns
a
> pathname object.
>
> > > + SI::CHDIR now takes a boolean as a second argument:
> > > (SI::CHDIR new-directory &optional update-d-p-d)
> > > If update-d-p-d is true, then *DEFAULT-PATHNAME-DEFAULTS* takes is set
> > > to the
> > > truename of the new working directory.
> >
> > Same here.  Is it exported?
>
> Same as SI::GETCWD: it is exported and it returns a pathname corresponding
to
> the current directory before it is changed.
>
> Regards,
>
> Juanjo
>
>
>
> --__--__--
>
> Message: 3
> Date: Thu, 8 Jan 2004 12:29:28 -0500
> Subject: Re: [Ecls-list] Xmas fixes
> Cc: ecls-list at lists.sourceforge.net
> To: Juan Jose Garcia-Ripoll <worm at arrakis.es>
> From: Marco Antoniotti <marcoxa at cs.nyu.edu>
>
> Thanks
>
> I just got confused, given that you wrote SI::GETCWD and SI::CHDIR.
>
> Cheers
>
> Marco
>
>
>
>
> On Thursday, Jan 8, 2004, at 12:18 America/New_York, Juan Jose
> Garcia-Ripoll wrote:
>
> > On Thursday 08 January 2004 17:42, Marco Antoniotti wrote:
> >>> + New function SI::GETCWD returns the current working directory of
> >>> the
> >>> C
> >>> library.
> >>
> >> Is this exported or not?  Doe it return a pathname?
> >
> > Yes, it is exported from the SYSTEM (or SI) package and it always
> > returns a
> > pathname object.
> >
> >>> + SI::CHDIR now takes a boolean as a second argument:
> >>> (SI::CHDIR new-directory &optional update-d-p-d)
> >>> If update-d-p-d is true, then *DEFAULT-PATHNAME-DEFAULTS* takes is
> >>> set
> >>> to the
> >>> truename of the new working directory.
> >>
> >> Same here.  Is it exported?
> >
> > Same as SI::GETCWD: it is exported and it returns a pathname
> > corresponding to
> > the current directory before it is changed.
> >
> > Regards,
> >
> > Juanjo
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Perforce Software.
> > Perforce is the Fast Software Configuration Management System offering
> > advanced branching capabilities and atomic changes on 50+ platforms.
> > Free Eval! http://www.perforce.com/perforce/loadprog.html
> > _______________________________________________
> > Ecls-list mailing list
> > Ecls-list at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ecls-list
> >
> --
> Marco Antoniotti http://bioinformatics.nyu.edu
> NYU Courant Bioinformatics Group tel. +1 - 212 - 998 3488
> 715 Broadway 10th FL fax. +1 - 212 - 998 3484
> New York, NY, 10003, U.S.A.
>
>
>
> --__--__--
>
> Message: 4
> Date: Thu, 8 Jan 2004 15:25:28 -0700 (MST)
> From: Dennis <dennis at illusions.com>
> To: ecls-list <ecls-list at lists.sourceforge.net>
> Subject: [Ecls-list] red hat linux 9 cvs build failure
>
> Hi,
>
> I am unable to build ecls from cvs on Jan 1, 2004.
>
> Below is what happens at the end of the make. I can send a transcript of
> the entire configure & make output if that helps.
>
>
> if [ -f CROSS-COMPILER ]; then \
>         touch ecl_min; \
> else \
>         gcc  -o ecl_min c/cinit.o -L./ libecl.a -lgmp -lgc -ldl -lm;\
> fi
> sed -e 's, at ecldir@,/usr/local/lib/ecl,g' < compile.pre > compile.lsp
> ln -s -f /home/dennis/src/ecls/src/cmp/sysfun.lsp ./
> if [ -f CROSS-COMPILER ]; then \
>         ./CROSS-COMPILER < compile.lsp; \
> else \
>         ./ecl_min < compile.lsp; \
> fi
> ;*** Lisp core booted ****
> ECLS (Embeddable Common Lisp)  16384 pages
>
> >
> Unrecoverable error:
> Lisp initialization error.
>
> make[1]: *** [ecl] Error 134
> make[1]: Leaving directory `/home/dennis/src/ecls/build'
> make: *** [all] Error 2
>
>
> --
> ---
> Dennis Sacks
> dennis at illusions.com
>
>
>
>
>
> --__--__--
>
> _______________________________________________
> Ecls-list mailing list
> Ecls-list at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ecls-list
>
>
> End of Ecls-list Digest
>





More information about the ecl-devel mailing list