Re: [agtk-devel] AGLIB tcl binding

[Haejoong L. <hae...@un...>]

> I've attached a version of ag.tcl which uses namespaces fyi.  I've put 
> everything into an AG namespace, including the AGF functions, I don't know 
> what the argument is for having them separate.  I've also capitalised 
> AG::Load and AG::Save for consistency with the rest of the interface. 

Thanks, but I can't find any attached file. Could you please send it
again?

> > I agree with you. Since we have multiple wrappers (currently two),
> > the following would be better:
> >
> >     ag_wrapper/
> >         tcl/
> >             ag.tcl
> >             ag_tcl.so
> >             pkgIndex.tcl
> >         python/
> >             ag.py
> >             ag_python.so
> >
> 
> This wouldn't work at least with tcl since tcl will only look for packages in 
> sibling directories to it's own installation dir (eg all dirs in 
> /usr/local/lib). I imagine that python is similar.  The main thing is to get 
> the tcl package files into one directory that can be installed in the right 
> place or bundled up to form a binary extension package.

I see.  However, the package name "ag" is too big for it.  How about
"ag_tcl"?  Does it need to be consistent with namespace name?


> > So we have some options here:
> >
> >     (libag + libagf), (tcl wrapper), (python wrapper)
> >     (libag + libagf + tcl wrapper), (libag + libagf + python wrapper)
> >     (libag + libagf + tcl wrapper + python wrapper)
> >
> > I guess you meant the first choice. 
> 
> Yes, and even the second choice as a compile time option. This would give me 
> one big shared object I could deliver with my application if I only use AG 
> vial the tcl (or python) interface.  

I'll try to make that a configuration option.


Thanks,
Haejoong