Date: Tue, 19 Mar 1996 15:16:08 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: nate@sri.MT.net (Nate Williams) Cc: terry@lambert.org, nate@sri.MT.net, msmith@atrad.adelaide.edu.au, kuku@gilberto.physik.rwth-aachen.de, jdp@polstra.com, nate@sneezy.sri.com, freebsd-hackers@freebsd.org Subject: Re: GAS question Message-ID: <199603192216.PAA24885@phaeton.artisoft.com> In-Reply-To: <199603192051.NAA04951@rocky.sri.MT.net> from "Nate Williams" at Mar 19, 96 01:51:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Fair enough. XEmacs has a 2-4MB footprint. But, X has an 8MB > footprint, and FreeBSD a 4MB footprint, so we have about the same memory > footprint. Windows95 does not have an 8M footprint. VCACHE.VXD does. And you can "fix" it. There are undocumented settings that allow you to manipulate its behaviour. Windows95 runs in 4M. That's 8M smaller than your "FreeBSD+X" footprint (which I don't believe anyway: I ran a lab full of 386's with 4M of memory running FreeBSD as X terminals). > I can run XEmacs in 8MB too, but it *really* slows the compiles down due > to thrashing. :) I can run VC++ in 8M without thrashing if I set the right configuration options. > > No thanks; i'm only interested in the IDE part. I'd like to substitute > > the editor for "vi" (like I do using the Microsoft tools). > > 'vi' is incapable of doing all of the necessary work. Can you replace > the editor in VC++ with vi? Can you replace it with *any* editor? (My > biggest beef with most PC tools is that you can't replace the editor > with your editor of choice.) You can edit it in a window, and the tools "know" the file has changed and reload it. The editor is configurable, and can in fact be made to look like vi with a lot of work (it some with default settings and a "Brief" template). > > This is retail price. This is not what you pay for an MSDN Level 2 > > SDK/DDK/VC++ subscription. > > I think I paid $695/yr for my L2 kit, plus another $495/yr for the > subscription. Now try to recover that in market for BSD programs. > VC++ isn't the compiler the OS team uses. They use a command line > compiler that is distributed with the L2 kit, not VC. (This according > to someone who works at M$ in their OS group.) You are confusing the replacement LINK386.EXE that shipped on the DDK CDROM. VC++ is now at 4.0, which includes the VXD-capable linker. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603192216.PAA24885>