Tweet
Note to Lance and Tom - I started a topic pretty much the same
as this one in the 3rd-party Forum. I know y'all dislike
cross-posting, so I deleted that original posting.
Here's the scenario: I have been in the process of creating a
PB/DOS 3.5 API to be used for writing programs that manipulate
the TriBBS BBS database files. Up until I stopped writing TriBBS
utilities/doors about 12 months ago, I was using a Freeware,
fully developed/debugged API that was written by one of the
previous trademark owners of the TriBBS BBS software.
The problem: that API written by the other fellow is a comprehensive,
exhaustive API, and is an EXCELLENT API, with ONE exception: he
somehow coded his PBU's/PBL so that programmers who use his API
*must* use $DIM ALL and DEFINT A-Z. Well, and I know it's being
iconoclastic, but I *hate* having to explicitly declare EACH and
EVERY variable in my source code. It's more of a pain than a help,
to me, anyway. 'Sides, I've NEVER had a problem with errant variable
names and I *never* use #DIM ALL (32-bit) or $DIM ALL, unless I
*have* to.
Finally, the question: do any of you experienced programmers, or
BBS Administrators, know of a way to stop the API from REQUIRING
$DIM ALL and DEFINT A-Z in my main program's source file in order
for it to compile? When I try to write/compile my source code
WITHOUT them, I always get an error message: DUPLICATE DEFINITION
on one or other functions contained within the PBL. Once I insert
the $DIM ALL and DEFINT A-Z back into the source, they compile just fine.
*IF* one of y'all can provide me with a workable solution/workaround,
then I'll drop my own API-writing project, as that other guy's is
already excellent (and Free), except for the noted irregularities.
Any ideas would be GREATLY appreciated!
Thanks in advance!
Cordially,
ADDENDUM: FYI, to whomever reads/answers this post, I can't ask
the other fellow for help on using his API. Up until 6 months
ago, we were on each other's ICQ Contact Lists. But, I'm afraid
I seriously offended him at that point. He's an all-the-way VB
fan, while I think it's needless "bloatware." Well, he had
written a TrIBBS Freeware files database program to assist
sysops in changing the drive letters in the database. But, like
is typical of VB code, it was "fat" and needed all kinds of
runtime dependencies. So, I wrote my own version of the program,
that did the same thing (albeit with a different user interface)
in PB. My program was only 23KB in size, twice as fast as his, and the
only runtime dependencies in it were the standard Windows API
DLL's. So, I "rubbed his nose in it." I did *specifically* tell
him that I was NOT making fun of HIM, or his programming abilities,
that I was just bashing VB. But, that was the last time he
corresponded with me. I deserved it, because I shouldn't have
rubbed his nose in it, even though I was doing it in jest.
Anyway, I apologize for this long addition to my original post -
I just want you other members to understand why I *can't* go to
the guy directly for his help with using his API.
------------------
Clay C. Clear
mailto:[email protected][email protected]</A>
Clay Clear's Software
[This message has been edited by Clay Clear (edited September 07, 2001).]
as this one in the 3rd-party Forum. I know y'all dislike
cross-posting, so I deleted that original posting.
Here's the scenario: I have been in the process of creating a
PB/DOS 3.5 API to be used for writing programs that manipulate
the TriBBS BBS database files. Up until I stopped writing TriBBS
utilities/doors about 12 months ago, I was using a Freeware,
fully developed/debugged API that was written by one of the
previous trademark owners of the TriBBS BBS software.
The problem: that API written by the other fellow is a comprehensive,
exhaustive API, and is an EXCELLENT API, with ONE exception: he
somehow coded his PBU's/PBL so that programmers who use his API
*must* use $DIM ALL and DEFINT A-Z. Well, and I know it's being
iconoclastic, but I *hate* having to explicitly declare EACH and
EVERY variable in my source code. It's more of a pain than a help,
to me, anyway. 'Sides, I've NEVER had a problem with errant variable
names and I *never* use #DIM ALL (32-bit) or $DIM ALL, unless I
*have* to.
Finally, the question: do any of you experienced programmers, or
BBS Administrators, know of a way to stop the API from REQUIRING
$DIM ALL and DEFINT A-Z in my main program's source file in order
for it to compile? When I try to write/compile my source code
WITHOUT them, I always get an error message: DUPLICATE DEFINITION
on one or other functions contained within the PBL. Once I insert
the $DIM ALL and DEFINT A-Z back into the source, they compile just fine.
*IF* one of y'all can provide me with a workable solution/workaround,
then I'll drop my own API-writing project, as that other guy's is
already excellent (and Free), except for the noted irregularities.
Any ideas would be GREATLY appreciated!
Thanks in advance!
Cordially,
ADDENDUM: FYI, to whomever reads/answers this post, I can't ask
the other fellow for help on using his API. Up until 6 months
ago, we were on each other's ICQ Contact Lists. But, I'm afraid
I seriously offended him at that point. He's an all-the-way VB
fan, while I think it's needless "bloatware." Well, he had
written a TrIBBS Freeware files database program to assist
sysops in changing the drive letters in the database. But, like
is typical of VB code, it was "fat" and needed all kinds of
runtime dependencies. So, I wrote my own version of the program,
that did the same thing (albeit with a different user interface)
in PB. My program was only 23KB in size, twice as fast as his, and the
only runtime dependencies in it were the standard Windows API
DLL's. So, I "rubbed his nose in it." I did *specifically* tell
him that I was NOT making fun of HIM, or his programming abilities,
that I was just bashing VB. But, that was the last time he
corresponded with me. I deserved it, because I shouldn't have
rubbed his nose in it, even though I was doing it in jest.
Anyway, I apologize for this long addition to my original post -
I just want you other members to understand why I *can't* go to
the guy directly for his help with using his API.
------------------
Clay C. Clear
mailto:[email protected][email protected]</A>
Clay Clear's Software
[This message has been edited by Clay Clear (edited September 07, 2001).]
Comment