On Sat, 6 Feb 2021 20:35:30 -0800 (PST)
At this point, you're completely sane. Hurray!
Post by Harry PotterI have a program I'm creating for C users
At this point, you're still completely sane. Yeah!
Post by Harry Potterusing VBDOS 1.0, and,
So, you're creating a program for C users which is coded in Visual
Basic? Yup, unh-huh, okay, gotcha ...
So, at this point, I'm thinking that you've /COMPLETELY/ lost it.
Um, tell me now, just what would you do with a program that someone
coded for VBDOS users using COBOL? ...
FYI, I actually had to look up what VBDOS was: M$ Visual Basic.
Anyway, I'm ROFL at the thought of this. Sorry if that irks you, but,
hopefully, my question above got the point across.
AISI, the only reason to /not/ code a program for C users using C to
do so, is to bootstrap C code. Almost no one needs to ever bootstrap C
code anymore, as everyone has access to a C compiler on every platform.
Lack of ubiquity is another reason to not use VBDOS. Yes, it's true
that the C users could port your program to C, if they wanted C code
instead of VBDOS code. However, they'd find it much easier to start
from nothing and recreate the functionality of your code, but entirely
coded in C. It's very easy to take the inputs to a program and the
outputs of a program and create new code that will do exactly the same.
--
Microsoft:"You can't fix it."
Linux:"You can't compile it."