IMPORT/CLOSE issues?

[Fairlight]

At Tue, Apr 11, 2006 at 11:50:17AM -0400 or thereabouts, 
suspect Kenneth Brody was observed uttering:
> No, LOOKUP and IMPORT/EXPORT differ on this aspect.

Cool.  At least I know the differences now.

> Well, like I said, you're thinking of IMPORT as open(), rather than as
> read()/fgets()/etc.

Well, yeah...I mean it's only logical that it must implicily do an open().
As such, and as I used it so long ago myself and so little that I now
thought for some reason you'd do one import and then many assignments
with new subscripts.  (I had that field/record thing entirely forgotten.)
Basically I was trying to think of it as a lookup, where there is indeed a
getnext.

You can tell I never really used this functionality much myself, right? :)
Didn't really need it much though.  By the time I was dealing regularly
with file-based rather than user-based input, I was able to use the raw I/O
layer that was added later.

> Well, just remember that the implicit open() only occurs if the file isn't
> already open.

Fair enough.  Noted for future.

> > Could be just me...but that's my take.
> 
> Yup, it's just you.  :-)

Again, fair enough.  :)  Thanks for the kind responses and explanations!

mark->