I agree with Alrescha: it looks like this 10.2.5 bug fix was somehow dropped on the floor with 10.2.6.
To see this ugly bug again is very frustrating. I've been wrestling with this problem since the 10.2 release, when it was apparently introduced with Rendezvous. Rendezvous uses multi-cast DNS, and required significant changes to the DNS code.
btw, why does the Slashdot server insist on inserting a space between the "254" and the "05" in the first line of my submission...???
...the answer is the same. I've been a consulting software engineering since 1996. I've always taken the approach that the professional and moral obligations of a consultant are the same as those of an employee.
The only differences between consultants and employees are:
(a) consultants are paid more. This is why we consult.
(b) consultants get older equipment. This is a bone thrown to lower paid employees.
(c) consultants have a different contract, and a different tax withholding status.
You should present your dilemma again, but this time leave out consultant vs. employee spin.
Actually in my original post I was suggesting a standard string library for C.
Yes, I gathered that when I re-read your post after submitting mine. My bad.
In defense of PTypes, its real value for me is its threading and networking abstraction accross mac, win, and various unixes. That's what I need for this project - no more, no less. The package is small, which is an advantage over something like ACE when it comes to making alterations, and making sure it runs on more obscure environments like the mac. The string class is a bonus. Another bonus is a thread-safe ref-counting scheme with a nice smart-pointer template on top of it.
But what about third-party libraries? Should they use the string class from PTypes, or from some other foundation library?
The PTypes string class seamlessly converts to/from (char*) and (const char*). As long as third-party libraries can handle these basic types, then the crossover is seamless.
For example this function:
pt::string m( pt::string s );
May be used like so:
printf( m( "hello world" ));
The 'S' in 'STL' is the most important letter.
I agree, although the STL has no threading or networking abstraction layer. I'm very comfortable using PTypes for that.
I think it would help if there were a standard, minimal C string library
Check out PTypes. To quote the PTypes home page:...a simple alternative to the STL that includes multithreading and networking. It defines dynamic strings...
I'm currently using it in a commercial project, and it's a nice package, well thought out, and quite stable.
Slashdot Mirror
http://docs.info.apple.com/article.html?artnum=254 05
I agree with Alrescha: it looks like this 10.2.5 bug fix was somehow dropped on the floor with 10.2.6.
To see this ugly bug again is very frustrating. I've been wrestling with this problem since the 10.2 release, when it was apparently introduced with Rendezvous. Rendezvous uses multi-cast DNS, and required significant changes to the DNS code.
btw, why does the Slashdot server insist on inserting a space between the "254" and the "05" in the first line of my submission...???
...the answer is the same. I've been a consulting software engineering since 1996. I've always taken the approach that the professional and moral obligations of a consultant are the same as those of an employee.
The only differences between consultants and employees are:
(a) consultants are paid more. This is why we consult.
(b) consultants get older equipment. This is a bone thrown to lower paid employees.
(c) consultants have a different contract, and a different tax withholding status.
You should present your dilemma again, but this time leave out consultant vs. employee spin.
Yes, I gathered that when I re-read your post after submitting mine. My bad.
In defense of PTypes, its real value for me is its threading and networking abstraction accross mac, win, and various unixes. That's what I need for this project - no more, no less. The package is small, which is an advantage over something like ACE when it comes to making alterations, and making sure it runs on more obscure environments like the mac. The string class is a bonus. Another bonus is a thread-safe ref-counting scheme with a nice smart-pointer template on top of it.
But what about third-party libraries? Should they use the string class from PTypes, or from some other foundation library?
The PTypes string class seamlessly converts to/from (char*) and (const char*). As long as third-party libraries can handle these basic types, then the crossover is seamless.
For example this function:May be used like so: The 'S' in 'STL' is the most important letter.
I agree, although the STL has no threading or networking abstraction layer. I'm very comfortable using PTypes for that.
I think it would help if there were a standard, minimal C string library
...a simple alternative to the STL that includes multithreading and networking. It defines dynamic strings...
Check out PTypes. To quote the PTypes home page:
I'm currently using it in a commercial project, and it's a nice package, well thought out, and quite stable.