I see your point.It makes sense.(Although there is a QBASIC compiler which
creates EXE's,which I use).I have found a solution too this problem (for
me).At least a half a month ago,I've started learning turboC++.In another
month,I should be ready to create simple programs for the community.(As far
as QBASIC,I'm just gonna step back on this one,as I don't wish to anger
anyone).So,I've started learning turboC++.I may still make the occasional
QBASIC program,but other than that,I will be making everything in C++.If
there is a problem with this,please respond back.I thank everyone for their
patience with this topic. :-)
-Jayden
On Mon, Jan 26, 2015 at 1:54 PM, Ralf Quint <freedos...@gmail.com> wrote:
> On 1/26/2015 1:27 PM, JAYDEN CHARBONNEAU wrote:
> > I have noticed that this is an explosive topic.Some people think it
> > doesn't matter the source,and others disagree.From what I'm reading (I
> > may be wrong),but it seems from what I'm reading in this discussion
> > that a program can only be submitted to freeDOS if it is made with a
> > specific compiler.
> Well, I think that there are two separate issue at hand here.
>
> 1) Jim (and a couple others) would like to see that each and every piece
> of software associated with FreeDOS is written in an Open Source
> programming language. There is not directly any definitive rule about a
> specific compiler or language being used, but at there is some general
> preference to use C, with the preferred compiler being used being first
> Turbo C (back in the good old days 8-) ) and later OpenWatcom, after it
> was released by Sybase as Open Source some 13/14 years ago.
>
> 2) another issue however is how well a certain language (or a specific
> implementation hereof) is suited for a certain task. For example, you
> are referring yourself to QBASIC,, which is an intepreter, requiring the
> QBASIC executable to be present to execute. That would eliminate it
> pretty much for a lot of low-level tasks, and not only for speed and
> memory requirement issues. It would be a pretty bad choice for a
> replacement or alternative for the existing command.com, just as
> command.com's batch processing "language" would be a (really) bad choice
> for a "security" program.
>
> Ralf
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
