Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Fri, 14 Feb 2003 20:07:09 -0500 Alex Pennace <alex at pennace.org> wrote: > It depends largely on the preference of the professor. For a few > semesters, when another professor took over for the normal Computing I > professor, he had everyone use Visual C++, and submit the full > workspace on a floppy disk. When the normal professor started teaching > the course again, it was back to using gcc on the Tru64. That is true. I teach the C Programming Language and do not dictate the tool. A good C program should compile and run on GCC on Linux, Unix, Cygwin or on Windows as a console app compiled under Visual C++. The assembler we built for Windows NT was developed under the Digital Unix C compiler which was installed on bith Digital Unix (eg Tru64) and Windows NT until Visual C++ was working on the Alpha. There were very few cases where we needed compiler specific ifdefs. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20030214/ada81c46/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |