Re: Import script

[José María González <chema@cs.berkeley.edu>]

I remember there were two problems with the 
tclcl/tcl-import.tcl script. The first one was 
the latter didn't ever complain. You can try: 

[elmer-fudd, 25] > mash
% import someinexistentclass
% 

which was not very helpful. 

Compare with import.tcl: 

[elmer-fudd, 28] > mash
% source [file join $env(TCLCL_IMPORT_DIRS) import.tcl]
% import someinexistentclass
*** warning: couldn't find info for the class someinexistentclass
% 

I think it seemed easier for me to write what I 
needed from scratch than fixing the original code, 
which is slightly bloated (import.tcl code is 200 
lines, compared to 900 for the tclcl/tcl-import.tcl). 
Or maybe I had it already written import.tcl when I 
knew about tclcl/tcl-import.tcl. 

There was another reason, but I cannot remember it :( 

-Chema




"Lawrence A. Rowe" wrote:
> 
> Andrew Swan wrote:
> >
> > Lawrence A. Rowe wrote:
> > > I created a import script that permits executing current
> > > mash otcl scripts without having to expand them previously.
> > > I found pretty annoying the need to "compile" my scripts
> > > everytime I modified them. The new script does the expansion
> > > process during run-time: instead of expanding every "import"
> > > command, now there is an actual import command that worries
> > > about everything. You can also execute "import" commands
> > > interactively.
> > > [...]
> >
> > how is this different from the built in code in
> > mash-code/tclcl/tcl-import.tcl ??
> >
> > -Andrew
> ---
> 
> no idea, i just included it because chema sent it around and someone had
> sent me email because he was having trouble running a script.
>         larry
> --
> Professor Lawrence A. Rowe          Internet:  Rowe@BMRC.Berkeley.EDU
> Computer Science Division - EECS       Phone: 510-642-5117
> University of California, Berkeley       Fax: 510-642-5615
> Berkeley, CA 94720-1776            URL: http://bmrc.berkeley.edu/~larry