Chuck's statement reflects Forth philosophy - don't try to make something more universal than it needs to be. Abstraction kills efficiency. You can't write code that runs on two different platforms without sacrifying performance. And Forth is about using every "mips" available. Some with user interface.
Color is used in ColorForth as attribute - by using color you denote function of word that you write - whether it is word to be defined, part of definition, statement to be executed or a comment. And as others have pointed out, you can use smell or tone or font typeface instead of color.
On the other hand, Chuck's ColorForth implementation will choke on my hardware, uses extremanlly big screen font and worse-then-dvorak keyboard layout. I think it is not intended for widespread use - more a testbed for interesting ideas.
Industry analysts have concluded that *BSD is declining. Let's look at the numbers.
I'm NetBSD user. I won't tell you whether there is 140, 1400 or 14000 NetBSD users because I don't really know. I can tell you that the number isn't declining - how did you draw such conclusion?
I haven't heard of BSD being sick - in fact we are having lots of fun writing BSD code.
> BFD
Yes, it is big deal indeed. NetBSD project doesn't release new version every day. NetBSD 1.4 was announced in May 1999.
And the changes are well worth new number. Soft updates in FFS, full featured RAID implementation, LFS improvements, Kerberos V and more cryptography support integrated (and available outside US as well), NFS lockd, IPv6 and various performance and reliability enhancements to name only a few.
Re:Compatibility support for Win32 programs??
on
NetBSD 1.5 released
·
· Score: 3
It means that NetBSD can run win32 binaries
(PECOFF format) just like those for Linux, NetBSD, Solaris, etc.
Basic system libraries (win32 API) have to be replaced by versions specifically written for NetBSD.
Look at compat_pecoff(8) (the manual page) and http://chiharu.haun.org/peace/ (libraries).
Slashdot Mirror
Chuck's statement reflects Forth philosophy - don't try to make something more universal than it needs to be. Abstraction kills efficiency. You can't write code that runs on two different platforms without sacrifying performance. And Forth is about using every "mips" available. Some with user interface.
Color is used in ColorForth as attribute - by using color you denote function of word that you write - whether it is word to be defined, part of definition, statement to be executed or a comment. And as others have pointed out, you can use smell or tone or font typeface instead of color.
On the other hand, Chuck's ColorForth implementation will choke on my hardware, uses extremanlly big screen font and worse-then-dvorak keyboard layout. I think it is not intended for widespread use - more a testbed for interesting ideas.
have something where the first, say, 10 elements of the stack are in registers, and the rest in memory.
Usually in Forth you won't put more than few elements on the stack. In fact one of Chuck's processors had stack only 5 cells deep.
While some software Forth systems give you 64 or more stack cells, it is advocated that good Forth program won't use more than 10 or 15.
Industry analysts have concluded that *BSD is declining. Let's look at the numbers.
I'm NetBSD user. I won't tell you whether there is 140, 1400 or 14000 NetBSD users because I don't really know. I can tell you that the number isn't declining - how did you draw such conclusion?
I haven't heard of BSD being sick - in fact we are having lots of fun writing BSD code.
> BFD
Yes, it is big deal indeed. NetBSD project doesn't release new version every day. NetBSD 1.4 was announced in May 1999.
And the changes are well worth new number. Soft updates in FFS, full featured RAID implementation, LFS improvements, Kerberos V and more cryptography support integrated (and available outside US as well), NFS lockd, IPv6 and various performance and reliability enhancements to name only a few.
It means that NetBSD can run win32 binaries (PECOFF format) just like those for Linux, NetBSD, Solaris, etc.
Basic system libraries (win32 API) have to be replaced by versions specifically written for NetBSD.
Look at compat_pecoff(8) (the manual page) and http://chiharu.haun.org/peace/ (libraries).