I did. And I read it again.
It's not at all clear that you ate explaining that the behaviour can only be seen in a script. I think everybody would be much happier if you tried to be a bit more polite. Especially when talking to people who are trying to help you. Regards, Elias On 7 Feb 2017 00:15, <[email protected]> wrote: > > did you read the post? > > i didn't ask about it in a workspace - my example was in a SCRIPT > > > On Mon, 6 Feb 2017 11:33:51 +0800 > Elias Mårtenson <[email protected]> wrote: > > > It works for me: > > > > Network listener started. Connection information: mode:tcp addr:40267 > > * )fns* > > * )copy 5 SQL* > > DUMPED 2017-02-06 11:25:33 (GMT+8) > > * )fns* > > SQL∆Begin SQL∆Columns SQL∆Commit SQL∆Connect > > SQL∆Disconnect SQL∆Exec SQL∆Rollback SQL∆Select > > SQL∆Tables SQL⍙metadata > > > > Regards, > > Elias > > > > On 6 February 2017 at 10:10, <[email protected]> wrote: > > > > > #!/usr/local/bin/apl --script -- > > > > > > 1 > > > ⍝⍎')copy SQL.apl' ⍝ for sqlite fns > > > > > > ∇sqlite > > > > > > 2 > > > ⍎')copy SQL.apl' ⍝ for sqlite fns > > > > > > ⍎')fns' ⍝ doesn't show SQL∆Connect > > > > > > db←'sqlite' SQL∆Connect '/sqlite/tutorial.db' > > > ⍝db←'sqlite' ⎕sql[1] '/sqlite/tutorial.db' > > > > > > .... > > > > > > > > > ∇ > > > > > > )fns ⍝ shows SQL∆Connect > > > > > > )off > > > > > > > > > > > > > > > the ⎕sql[1] is in the apl so using it doesn't require anything but > > > starting apl > > > > > > the SQL∆Connect is a fns in the SQL.apl so to use it the )copy must be > done > > > > > > the question is why doesn't the 2 )copy in the sqlite fns bring in the > > > function SQL∆Connect until after the sqlite function is run - it says > > > dumped? > > > > > > if i uncomment the 1 )copy the SQL.apl fns are loaded > > > > > > it is the same behavior in apl workspace > > > > > > > > > > >
