Aside from performance difference, it might had been better for us  
running on Mono CLR or JVM, since at least it would compile and work.   
Then again, no one can tell us why they switched to C++, not much of  
GNOME has gone that direction, why GSM?

I don't care either way being in either past or present, but hopefully  
some workaround can be implemented, or perhaps fork their last C  
release and add similar features.  It seems that this would be the  
only logical way for Sun to go since they are so committed and  
arrogant with their compilers, which lack the needed support.  I'm all  
for standards, but in this case there's really nothing we can do,  
except yell at the GNU folks for using non-standards and adding every  
option into every program for even the most obscure and stupid  
reasons, well that's just GNU.  The whole kitchen sink routine in  
plain sight for all to suffer from.

James
On May 29, 2008, at 5:51 AM, Kaiwai Gardiner wrote:

> On Thu, 2008-05-29 at 00:35 -0700, hua zhang wrote:
>> Sorry, in fact I also don't know the actual reason. Maybe they want  
>> to
>> practise C++ programming.. :)
>>
>>
>> This message posted from opensolaris.org
>> _______________________________________________
>> desktop-discuss mailing list
>> desktop-discuss at opensolaris.org
>
> Well, atleast it wasn't Java, C# or *shudder* some other god awful
> language. Then again, the studio developers need to rattle their dags
> and get on with implementing things that GCC has - or otherwise it'll
> end up making Suns studio package look like a joke in the developer
> community - unless of course someone here wishes to volunteer to
> re-write the portions of gnome system monitor unsupported by Sun
> Studio's C++ compiler.
>
> Matthew
>
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20080529/763989b1/attachment.html>

Reply via email to