The easy way to get rid of the warning seems to be:
changing:
using goguts
in my program to:
include("goguts.jl")
-------
No scope hassles so far...On Sun, Aug 2, 2015 at 12:15 PM, Forrest Curo <treegest...@gmail.com> wrote: > I have a program which uses Tk and Cairo to draw a gameboard in a window. > I would like to put this as a function in a larger program; but the window > and board persist and remain accessible only while the loop in that program > continues to run. > > Okay, then, if I want to avoid clutter in the parts of the program that > actually do anything, I can put them into a function and call that function > each time the loop repeats.... > > This works, but I get a warning: 'requiring "goguts" did not define a > corresponding module.' > > If I put the words "module" and "end" around my function, I no longer get > the warning, but the arrangement stops working! > > Functions and variables defined in the original program stop being > recognized in the new module; and if I put them into a third module it all > turns to muddle. > > Should I just leave out the stuff about 'module' and go on getting the > warning? -- or is there some way this kind of looping structure is properly > supposed to be handled? > >
