Thanks Jeremy. I've been playing with the kernel for the last few days and building it with OW v1.9. All looks quite good and the kernel seems to behave properly.
I definitely agree that source code should be written to be as portable as possible, and we can achieve that by coding to a standard such as C99. I've seen a few places where things like asm statements have crept in, and this isn't a major issue. We should try to refactor the code some time in the future to improve portability, but it isn't a pressing issue. I built freecom last night, and will probably try building with OW over the weekend. Should give me a good idea as to how hard the suggestion may be. Pat Project Coordinator On Sat, Aug 21, 2010 at 8:49 AM, Kenneth J. Davis <[email protected]> wrote: > On Sat, Aug 21, 2010 at 12:44 AM, Pat Villani <[email protected]> wrote: > > Folks, > > > > I'm thinking it would be a good idea to standardize on one C/C++ compiler > > for the project. I'm looking at the Open Watcom compiler and would like > > your opinion. Reason for this suggestion is that it is the only real > mode > > compiler still under development and supported. > > > > This doesn't mean that I want to drop the build options currently in our > > source code. Instead, I'd like to add Open Watcom to FreeCOM, install > and > > memory configs and build official releases with Open Watcom. > > > > Care to share? > > > > Pat Villani > > Project Coordinator > > > > I agree we should officially standardize on Open Watcom. I believe > unofficially we started switching to it a while ago, and all recent > release kernels are built with OW. I would like to add that when > feasible [desirable, applies to the program, not too much of burden, > ...] we should use OW 1.9 (or later) with its long file name support > and when it does not adversely effect the DOS version, effort should > be made to support* portability in terms of of source compilable with > other compilers and/or ability to compile with OW to its other target > OSes. (* I do not mean to imply writing code for other > compilers/platforms, but when writing/modifying keeping them in mind > and choosing design decisions accordingly.) > > Jeremy Davis > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Freedos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-devel >
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
