[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] Re: GCL 2.6.7 and init_* function name problem
From: |
Camm Maguire |
Subject: |
[Gcl-devel] Re: GCL 2.6.7 and init_* function name problem |
Date: |
04 May 2005 14:03:08 -0400 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Greetings!
<address@hidden> writes:
> Camm,
> With regard to the upcoming 2.6.7 release, is it possible that the following
> issue involving the init_* function name
> will be fixed? I need to know whether I'll have to rename some of my ACL2
> files in order to continue to use
> profiling...
> Thanks,
> David Hardin
> ----- Forwarded by David S Hardin/CedarRapids/RockwellCollins on 05/02/2005
> 05:33 PM -----
> David S Hardin/CedarRapids/RockwellCollins wrote on 03/22/2005 02:22:02 PM:
> > Camm Maguire <address@hidden> wrote:
> >
> >
> > > > 2) Always toggle the init_ name, and expand our currently crude
> > > > translation to ensure that we always come up with a valid C
> > > > identifier. (Right now, we only translate - to _)
> > > >
> > > > Would that solve David Hardin's problem, as follows?
> > > >
> > >
> > > Yes. If you'd like, I can post a simple patch achieving these three
> > > points.
> > > > P.S. In building the distributed books for profiling, I found that
> > > > having a file named @whatever.lisp (as in books/ihs/@logops.
> > > lisp) is a bad
> > > > idea.
> > > > In particular, the init function is given the name address@hidden(),
> > > > which is not a legal C identifier.
> > > >
> > > > P.P.S. A similar situation exists for the "near+" files found, for
> > > > example, in books/rtl/rel4...
> > > >
> > Camm,
> >
> > As you're going about this work, keep in mind that files in
> > different ACL2 books can have the same simple name, e.g. top.lisp
> > occurs in several of the distributed ACL2 books. I have been bitten
> > by this one today in my attempts to perform a COMPILER::LINK made up
> > of multiple books from many directories.
> >
> > Thanks again for trying to simplify this whole area for users -- I
> > think it will pay dividends in the long term.
> >
Yes, I am working on a solution for 2.6.7 and HEAD which should fix
this.
Mike, I think we also need to ensure that pathnames with nil directory
components can be opened on windows (i.e. should default to cwd).
Take care,
> > David Hardin
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gcl-devel] Re: GCL 2.6.7 and init_* function name problem,
Camm Maguire <=