On Wed, 18 Feb 2004 14:24:24 -0600, "Michael A. Clem"
<mclem@[EMAIL PROTECTED]
> wrote:
<snip>
>If you have access to VB, then it *can* be used procedurally. When
>setting up a project, you simply create a .bas file and in the Project
>options, tell it to start with the .bas file instead of a form. Within
>the .bas file, you can Show forms whenever you need them (if you need
>them). Somewhere on the internet (I've forgotten where) somebody
>explains how to use VB for plain, old console programs.
Yes, that can be done. But the minute you use forms or any other GUI
thing, they become event driven. And if you want to use a console,
you have to allocate it yourself, and write all the routines to use
it. Like PRINT, LOCATE, COLOR . . . And you can't always use the
correct name - PRINT is a reserved word - so you can't write your own
PRINT subroutine. And the list goes on. Also, the resulting EXE is
still marked as a GUI app, so you have to change that. And, finally,
no matter what you do, you still need the many megs of VB DLL's.
All this nonsense is part of the reason that I wrote BCET.
<snip>
--
Arargh402 at [drop the 'http://www.'
from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
To reply by email, remove the garbage from the reply address.
|
