> will be getting involved, using gosubs is out of the question.  Global
  > variables would get out of hand, and of course you run into the problem
  > of different subroutines using the same variable names.  Much better to
 
TJ>         I think that one person should decide upon a set of global
TJ>         variables.  Your going to need them eventually.  Then each
TJ>         writer will have a list of the variables that they CANNOT use 
TJ>         any other fashion.
 
There is nothing wrong with global variables, but, one thing about
using true subs and functions is you can have local variables and it
doesn't matter if the variable names are the same or not in some other
routine.  For a program as large as a bbs software package that will
have many hands involved it is unreasonable to expect all variables to
be tracked.  What about FOR/NEXT loops?  Or temporary/scratch
variables?  If someone invariably uses the global variable name in
their routine incorrectly the problem may be subtle and difficult to
track.  Best to write each routine as a "black box" that you know
exactly what is passed in and out of it.  Mind you, i am saying this
because this is a group project.  my own stuff, i use gosubs and global
variables consistently.  it is quick and fast and easy to do.  
 
TJ>         Ohh, I got my PB demo today.  While I am impressed with the ov
TJ> features and options, the IDE is just plain UGLY!  ;-)  If I could atl
TJ> change the colors to my liking I would be MUCH more happy.
  
The non-demo version comes with a PBINST program that lets you change
the colors.  it may even let you select your own.  i always use the old
turbo basic 1.1 colors since i was weaned on tb way long time ago and
am used to those colors.  the default pb colors arn't my cup of tea
either, in fact i usually get right out of it and run the pbinst if it
has the wrong colors.    eric
--- QM v1.00
---------------