Search results

Close, but not quite. The PPC is designed with expandibility in mind, much like MIPS. Chips like the G3/G4 can load data from RAM not just as 32-bits, but as 8/16-bit chunks too (doing the needed work to make it fill the 32-bit register correctly). This applies to storing data to RAM as well...

Depends on the stack, are you using a stack someone else wrote or your own? If it is your own, it is pretty easy, just make sure you store pointers to both the base and the top of the stack, and use a double-linked list for the stack's storage. That way your searches can start from the top or...

Searches aren't that bad on the older G3s, it is the indexing hit from starting up the system into Tiger. It sucked down 50% of my CPU for 8 hours worth of uptime before the main index was built. After that it isn't so bad... but still, I would call that a noticable, and rather significant...

I mis-read one of the posts that seemed to ask if current apps will run faster on Tiger because of the GCC 4.0 stuff if it wasn't recompiled. My bad.

Spotlight is rather sluggish because of the indexing involved... It is actually quite similar to MacOS 9's indexing, so on older machines it tends to suck down quite a few resources, more than it needs to.

Well, it is more along the lines of nearly impossible to quantify just yet. Most software is written and compiled using 3.3 currently, so it will continue to run as it has under Tiger. Tiger itself and its speedups aren't always gonna affect the apps directly, not to mention that there was a lot...

Skylarov's case falls under electronic documents, which it is harder to provide a case for space shifting here in the US. Space shifting for PDFs is equivilent to being able to print it in most cases. Which is /usually/ (not always) provided by Adobe's DRM, making their case against Skylarov...

Well, the section of the paragraph that got snipped referred to a court case, (which I wish I could remember the references I had to it) where a case was struck down. This case involved someone being sued under the DMCA for taking a protected CD and ripping the tracks onto his MP3 player. This...

Satire is lost on you. ;) This is true, at my high school we had a group of people get an MCSE, that is just how useless it is. Wow, such DeVry hate. The funny part is that those of us going to DeVry for a semi-reasonable degree make fun of the guys getting tech certs too. ;)...

Uh, almost. DMCA pertains to circumventing DRM. DRM has been implemented on many media formats, and all of it covered. DVDs just have 'DRM' support required by the standard, so it is more common. However, IIRC, a court case in the US ended awhile back where the judge stated that the DMCA...

Carbon vs Cocoa doesn't really mean much. Cocoa is actually noticably slower in particular areas, unless you like writing internals to replace the blockages Cocoa has for game-oriented development. Carbon and Cocoa these days aren't much different except Cocoa abstracts you from the hardware...

This is very true, and I expect it to remain this way for a long time. Those who already have OS 9 might keep using it for awhile to come, but those who don't already have it, aren't likely to want/need a copy. I have an old copy of PageMaker, and I have nearly zero reason to upgrade for my...

Uh, wow... I can't tell the sarcasm and jokes from the serious questions and responses anymore... :rolleyes: On a more serious note, Phil Schiller is on Apple's board of directors. He is directly involved with the Macintosh line, if I recall directly.

But it isn't like running 68000 code on a PowerPC. (Which is emulation) In this case, it is closer to running OS 9 within a sandbox. The newest hardware /can/ run it, but it just can't boot it (because the knowledge of the OF and hardware isn't in OS 9 for it to boot properly). The thing...

Actually, it wouldn't be as bad as you think. Several components would be shared between the two cores (which really is a copy of the key aspects like the registers, pipeline, and processing units). The connection to the outside world would be shared, and possibly a few other components...

Oddly, I think I found a possible explination of the impact I was seeing in 8A294: Granted, I know this is MacOS Rumors which has the tendancy to be slightly off in their grapevine, but if this is true, that would definitely explain the impact I saw, because it was definitely consuming 100%...

Yes, thank you. The PPC spec states how instructions work. Every instruction (well, nearly every instruction) specifies how many bits you want the result to be in. So when you load a number into a register, you have to specify how many bits are going to be loaded. (8, 16, 32, and now 64 are...

(void) typecasts are invalid constructs in C, as void is the 'lack of a type'. (void *) is still valid, but is still a pointer, just like an int pointer or a long pointer, or every other type. In fact, a pointer is always the same size: the native size of the processor the code was compiled for...

Yeah, it wreaks havoc if you let it. The thing is, if you wrote that code and compiled with gcc 3.3 on a 32-bit system... it will NOT behave any differently on a G5. The pointers were manipulated using 32-bit math instructions, so as I said, you get a 64-bit number with only 32 bits of...