SPISPOPD was apparently invented by people who were tired of discussing rumours about the then-unreleased Doom. id included the cheat code as a reference to this.
PhoenixNet does not involve the BIOS somehow directly interfering with your Internet connection. That would be absurdly difficult to implement. It actually appears to hook into the Windows setup procedure somehow. If you don't run Windows, you need never know about this.
Maybe you should read and learn something. One of the problems with 'CML1' is that there is no core configuration code and no formal definition of the format for option definitions. In 'CML1', 'make config' uses the shell as an interpreter for option definitions. It works through each of them in turn. This is not very easy-to-use, so 'make xconfig' and 'make menuconfig' parse all the option definitions and then provide random access to them. They each have a different parser, which is certainly less sophisticated than the shell's parser.
You're thinking of the issue of source file dependencies, which are something separate and are not addressed by CML2. There is a separate project to replace the current recursive make and kluged dependency analysis with something that works properly.
Re:But can you debug your programs?
on
GCC 3.0 Released
·
· Score: 2
The VC++ debugger will certainly show the contents of a std::string if you use the supplied standard library. I'm not sure how you would expect it to support replacement libraries.
Re:FOR loops: a question, ANSI C++, C++98, C++99..
on
GCC 3.0 Released
·
· Score: 2
Using macros to redefine keywords generally results in undefined behaviour (standard paragraph 17.4.3.1.1.2), so one's sensibilities should be offended. As a compiler-specific workaround this macro definition is obviously a necessary evil, but it should never be included in code that is meant to be portable.
VC++ 5.0 and 6.0 shipped with an old iostream library (iostream.h etc, global namespace) and a mostly standard C++ library including iostreams. The standard C++ library was provided (indirectly) by Dinkumware. Due to a legal dispute between Dinkumware and the company in the middle, this wasn't updated in 6.0 and so was not updated to match the standard (in any case, the VC++ compiler could not support all library features). This should be fixed in VC++ 7.0 (currently in beta, AFAIK).
Telephone links are a great idea. The problem is the fact that they can be disguised. Newer i-mode phones always show the number and give a prompt before dialling. The WAP standard that defines similar features requires prompting as well; hopefully manufacturers will learn from this and always prompt.
i-mode mailers don't support attachments; nor are they supposed to support HTML, but some of them do. Anyway, it's possible to put a link to tel:110 in a page, or sometimes in email, and to disguise it. Recent i-mode phones will always show the number and ask for confirmation before dialling, but older ones did not.
This is what every Amiga advocate used to say - because multi-tasking was just about the only thing the AmigaOS had going for it to start off with, along with a reasonable (but slow) file-system. For a long time it was horribly buggy, and it had a hideous and inconsistent UI. I was once Amiga advocate, but I doubt I would have been if I hadn't started out with OS 2.0.
Windows NT and all versions of Windows from Windows 95 onwards most certainly have real multi-tasking and multi-threading. On Windows 95 this can be crippled by Win16 apps, some of which were part of the OS distribution, but I don't believe that's true of later versions. So I think you're going on out of date information.
The hand-holding-disk was indeed the prompt to insert the Workbench disk (or another bootable disk) in AmigaOS 1.2 and 1.3. (Later versions had an animated disk beside the checkmark logo.) The original Amiga (later named the Amiga 1000) loaded the OS kernel from the Kickstart disk at power-on, and the prompt to insert that was a 'doodle-oot' noise.
The mobile phones that I know of use frequencies around 800 (AMPS and others), 900 (GSM), 1800 (GSM) or 1900 (all PCS) MHz. I' m not aware of any ~1300 MHz band.
WAP can be used on top of IP. WAP phones on the GSM system normally make a circuit-switched GSM data connection and run PPP and UDP/IP on top of that. The WAP-specific protocols then sit on top of UDP. GPRS, the "2.5G" high-speed packet system for GSM supports IP directly, so WAP-GPRS phones also use UDP/IP. UMTS, which is the 3G version of GSM, will assign an IPv6 to each handset and use IPv6 for everything, including voice calls.
Right, and it'll be using WAP over GPRS. Maybe not WML though - WAP doesn't rule out other formats. DoCoMo is exporting the i-mode brand, or maybe only their experience in marketing and ensuring usability, rather than any technology.
Scientology is based not on science but on the inventions of L Ron Hubbard, a one-time writer who appeared to have trouble distinguishing between fiction and reality. LRH had a similarly weak grasp of science to Chiu but sadly had quite a lot of success in proof by repeated assertion.
...if the Globalstar phones are any indication (and they should be, as its a pretty similar system) the biggest difficulty is keeping the antenna on a satellite
Based on what I see on their web site, I think that just pointing the aerial straight up is sufficient. Perhaps this is is only true in marketing land.
Read the Iridium service details carefully. The 'data service' (data calls to anywhere, presumably converted to standard modem protocols at the PSTN gateway) 'offers a data rate of up to 2.4 Kbps', which is the figure I recall from previously reading about Iridium.
The 'Internet data service' (which appears to mean using Iridium as your ISP) 'utilizes transparent compression, resulting in a data rate of up to 10 Kbps, depending on content' (my emphasis). So no, Iridium didn't suddenly get faster or start supporting channel bonding. I suspect that the standard data service probably includes such compression too, but the marketing department just forgot to include this misleading statement in its description. This does not turn a 2400 bps connection through Iridium into a 10 kbps connection any more than MNP5 (included in any ordinary modem) turns your 50 kbps connection through the PSTN into a 200 kbps connection.
Seems like he put them on the Golden Gate Bridge in one book and the Bay Bridge in another. I don't think there were squatters on both in either book. Weird.
.NET is not based on COM - it's a replacement for COM. It has some similarities, but it has major differences - generation of native code at run-time, garbage collection rather than reference counting, the Common Language Runtime, complete type descriptions, etc.
That said, Hailstorm is going in the direction of a Microsoft Planet.
This must be the realisation of the Microsoft network as envisioned in The Road Ahead.
Re:It's good to see a modern, fresh perspective...
on
The Humane Interface
·
· Score: 1
You can change the look and feel of most types of widget independently.
IETF vs ICANN? I don't think so.
on
IETF vs. ICANN
·
· Score: 1
The ICANN document this article refers to in turn refers to RFC 2826, published by the Internet Architecture Board. It seems to me that that is about as close as you're going to get to an official statement from the IETF on this. So it looks to me like it's Simon Higgs (perhaps supported by famed namespace-abuser Richard Sexton) vs the sane world.
Slashdot Mirror
SPISPOPD was apparently invented by people who were tired of discussing rumours about the then-unreleased Doom. id included the cheat code as a reference to this.
It goes on to list specific 'examples' of such licences, including the GPL and other licences.
PhoenixNet does not involve the BIOS somehow directly interfering with your Internet connection. That would be absurdly difficult to implement. It actually appears to hook into the Windows setup procedure somehow. If you don't run Windows, you need never know about this.
Maybe you should read and learn something. One of the problems with 'CML1' is that there is no core configuration code and no formal definition of the format for option definitions. In 'CML1', 'make config' uses the shell as an interpreter for option definitions. It works through each of them in turn. This is not very easy-to-use, so 'make xconfig' and 'make menuconfig' parse all the option definitions and then provide random access to them. They each have a different parser, which is certainly less sophisticated than the shell's parser.
You're thinking of the issue of source file dependencies, which are something separate and are not addressed by CML2. There is a separate project to replace the current recursive make and kluged dependency analysis with something that works properly.
The VC++ debugger will certainly show the contents of a std::string if you use the supplied standard library. I'm not sure how you would expect it to support replacement libraries.
Using macros to redefine keywords generally results in undefined behaviour (standard paragraph 17.4.3.1.1.2), so one's sensibilities should be offended. As a compiler-specific workaround this macro definition is obviously a necessary evil, but it should never be included in code that is meant to be portable.
VC++ 5.0 and 6.0 shipped with an old iostream library (iostream.h etc, global namespace) and a mostly standard C++ library including iostreams. The standard C++ library was provided (indirectly) by Dinkumware. Due to a legal dispute between Dinkumware and the company in the middle, this wasn't updated in 6.0 and so was not updated to match the standard (in any case, the VC++ compiler could not support all library features). This should be fixed in VC++ 7.0 (currently in beta, AFAIK).
Telephone links are a great idea. The problem is the fact that they can be disguised. Newer i-mode phones always show the number and give a prompt before dialling. The WAP standard that defines similar features requires prompting as well; hopefully manufacturers will learn from this and always prompt.
i-mode mailers don't support attachments; nor are they supposed to support HTML, but some of them do. Anyway, it's possible to put a link to tel:110 in a page, or sometimes in email, and to disguise it. Recent i-mode phones will always show the number and ask for confirmation before dialling, but older ones did not.
This is what every Amiga advocate used to say - because multi-tasking was just about the only thing the AmigaOS had going for it to start off with, along with a reasonable (but slow) file-system. For a long time it was horribly buggy, and it had a hideous and inconsistent UI. I was once Amiga advocate, but I doubt I would have been if I hadn't started out with OS 2.0.
Windows NT and all versions of Windows from Windows 95 onwards most certainly have real multi-tasking and multi-threading. On Windows 95 this can be crippled by Win16 apps, some of which were part of the OS distribution, but I don't believe that's true of later versions. So I think you're going on out of date information.
The hand-holding-disk was indeed the prompt to insert the Workbench disk (or another bootable disk) in AmigaOS 1.2 and 1.3. (Later versions had an animated disk beside the checkmark logo.) The original Amiga (later named the Amiga 1000) loaded the OS kernel from the Kickstart disk at power-on, and the prompt to insert that was a 'doodle-oot' noise.
The mobile phones that I know of use frequencies around 800 (AMPS and others), 900 (GSM), 1800 (GSM) or 1900 (all PCS) MHz. I' m not aware of any ~1300 MHz band.
WAP can be used on top of IP. WAP phones on the GSM system normally make a circuit-switched GSM data connection and run PPP and UDP/IP on top of that. The WAP-specific protocols then sit on top of UDP. GPRS, the "2.5G" high-speed packet system for GSM supports IP directly, so WAP-GPRS phones also use UDP/IP. UMTS, which is the 3G version of GSM, will assign an IPv6 to each handset and use IPv6 for everything, including voice calls.
Right, and it'll be using WAP over GPRS. Maybe not WML though - WAP doesn't rule out other formats. DoCoMo is exporting the i-mode brand, or maybe only their experience in marketing and ensuring usability, rather than any technology.
Scientology is based not on science but on the inventions of L Ron Hubbard, a one-time writer who appeared to have trouble distinguishing between fiction and reality. LRH had a similarly weak grasp of science to Chiu but sadly had quite a lot of success in proof by repeated assertion.
Based on what I see on their web site, I think that just pointing the aerial straight up is sufficient. Perhaps this is is only true in marketing land.
Anyway, does Iridium not support call hand-off?
Read the Iridium service details carefully. The 'data service' (data calls to anywhere, presumably converted to standard modem protocols at the PSTN gateway) 'offers a data rate of up to 2.4 Kbps', which is the figure I recall from previously reading about Iridium.
The 'Internet data service' (which appears to mean using Iridium as your ISP) 'utilizes transparent compression, resulting in a data rate of up to 10 Kbps, depending on content' (my emphasis). So no, Iridium didn't suddenly get faster or start supporting channel bonding. I suspect that the standard data service probably includes such compression too, but the marketing department just forgot to include this misleading statement in its description. This does not turn a 2400 bps connection through Iridium into a 10 kbps connection any more than MNP5 (included in any ordinary modem) turns your 50 kbps connection through the PSTN into a 200 kbps connection.
Golden Gate Bridge? Surely the Bay Bridge?
[FX: searches for "gibson squatters bridge"]
Seems like he put them on the Golden Gate Bridge in one book and the Bay Bridge in another. I don't think there were squatters on both in either book. Weird.
Microsoft is.
.NET is not based on COM - it's a replacement for COM. It has some similarities, but it has major differences - generation of native code at run-time, garbage collection rather than reference counting, the Common Language Runtime, complete type descriptions, etc.
This must be the realisation of the Microsoft network as envisioned in The Road Ahead.
You can change the look and feel of most types of widget independently.
The ICANN document this article refers to in turn refers to RFC 2826, published by the Internet Architecture Board. It seems to me that that is about as close as you're going to get to an official statement from the IETF on this. So it looks to me like it's Simon Higgs (perhaps supported by famed namespace-abuser Richard Sexton) vs the sane world.
There is not a single point of failure. There are something like 14 root name servers, and the security of each one is taken very seriously.