04 May 95 06:31, Chris Adams wrote to Lou Sanders:
 LS>> [ECHO PROJECT] VERB PROPOSAL
Hello Chris! Hello ALL!
 LS>> Since we decided on a "FrontEnd", "BBS" and "Tosser",  I feel the
 LS>> FrontEnd Mailer would be first thing we should start. If anyone
 LS>> feels otherwise then, by all means say so.
 CA> I'll go on record as agreeing with this one!
Then, may I suggest we get started... :)
CA> PowerMAILER? (Cheapie knockoff)
Okay, sounds good to me...
 CA> Your verb list looked pretty good. The only problem I have, and it's
 CA> not entirely related,
I not sure what you mean by "not related", it looks related to me. :)
Why do you say this???
 CA> is that it would be nice to decide how we can manage this.
 CA> If it was just me, I'd use the INI routines from
 CA> PB/VISION, but others may not have them. Any suggestions?
I not knocking this library, it's probably a great library, but I'm not 
familiar with it.
The problem I see with this type of library is, we don't have the source 
code, one, AND like you said above, not everyone will have this library.
I think all the functions, subs and other routines, we intend to use should 
be written by us, "THE PROJECT." Remember this project is also a teaching aid 
and I'm sure we all want to see, from the bottom up, how it all fits. There's 
no better way to learn, then seeing code and how it's used.
I hope this helps explain a litte more about the verb list... The not related
part, I didn't get... maybe not all the verbs are related but most of them 
should be. Anyway it was a start...
1. The setting up of the INI file can be done with any old text editor,no
   special tools will be needed. It can be read and altered with Qedit or
   whatever editor one might want to use. This means we don't have to build
   a configuration frontend to build a config file. "NOT AT THIS POINT!"
2. Reading the INI file would be done in two steps. If the verb is singular,
   meaning it can only appear once in the INI file, then the arugment 
following
   the verb is read on the first pass. If the verb CAN appear more then once
   in the INI file, an array could be used and the COUNT would be obtained on
   the first pass and the argument read in to the arrray on the second pass.
   The reason for having two passes is, it would allow the verb to be placed
   by the user on any line in the INI file, it adds a little flex and
   we don't end up having to say, "A" before "B" and "B" before "C", ect...
For Example:
   The verb "Baud_Rate" would only be used once in the INI file and the
   argument would be read on the first pass.
   On the other hand, the verb "Also_Known_As", may appear more then once. So
   we count the number of "AKA" verbs, dimension our array and on the second
   pass we read in the argument and Incr it's count... I should note: on the
   second pass, we would only be looking for verbs, we know can appear more
   then once. Example below...
STEP #1........
   OPEN "PowerM.INI" for input as #1
   do
   Line Input #1,LN$
   if UCASE$(LEFT$(LN$,9)) = "BAUD_RATE" then
    BaudRate$ = LTRIM$(RTRIM$(MID$(LN$,10)))
   end if
   if UCASE$(LEFT$(LN$,13)) = "ALSO_KNOWN_AS" then
     INCR AKAcount%
   end if
   Loop until Eof(1) = %True
   Close #1
Step #2.........
   Dim AKA$(1 TO AKAcount%) 'We have the count from step #1
   AKAcount% = 0 'Lets start over with our count
   OPEN "PowerM.INI" for input as #1
   do
   Line Input #1, LN$
   if UCASE$(LEFT$(LN$,13)) = "ALSO_KNOWN_AS"  then
    INCR AKAcount%
    AKA$(AKAcount%) = LTRIM$(RTRIM$(MID$(LN$,14)))
   end if
   Loop Until Eof(1) = %True
   Close #1
==== End of sample ===
Now, VERBS that have more then one argument on the same line will require a 
parsing routine. Multiple arguments should be separated by a single space,
this keeps the parsing routine simple. The "%" sign would be a comment or
a remark and would be ignored.
TTYL:
Lou Sanders
--- GoldED/2 2.50.Beta5+
---------------