WOO-HOO congrats to EVERYONE who voted and/or cared.Nice job Princec, it's been a long time, but there ya go :-)

---------------------Hmmm, after careful review, I may have jumped the gun on this.The category changed, but that doesn't mean it's going to production so to speak. :-(Just that it's actively being research, I s'pose that's a good thing, but not THE good thing I thought it was.Tape at 11am....

We should write a pure Java reference implementation that makes an ObjectBuffer and uses annotations to determine the offsets of the fields. It would be slow but it might serve to get the point across better.

You already know how to use libraries (jar files) when compiling, now as annotation processing is a part of any Java compiler, libraries can use annotation processing and automatically generate boiler-plate code for you. A possible example of this is RFE 4820062. I plan to elaborate more on this in a future entry.

So do us a favor and let us know what is wrong with the performance of the java.nio buffers if it doesn't meet your needs. That is a realistic way of solving your problems. Asking for C structs is not.

So do us a favor and let us know what is wrong with the performance of the java.nio buffers if it doesn't meet your needs. That is a realistic way of solving your problems. Asking for C structs is not.

A reply with such attitude is hard to believe to be official from Sun. Yet it is... it sounds like somebody took a personal offense regarding this request.

And we're not even asking for C-structs. A StructBuffer or an ObjectBuffer is a whole different thing, the only thing they share is the name, which might be the most important reason it gets so much hostile reactions.

Hi, appreciate more people! Σ ♥ = ¾Learn how to award medals... and work your way up the social rankings!

So do us a favor and let us know what is wrong with the performance of the java.nio buffers if it doesn't meet your needs. That is a realistic way of solving your problems. Asking for C structs is not.

I'd post a new artikel, forget about the votes adleast theres clarity then and just post a link to it in a comment. It seems sun is getting lost in the 4 pages of comments.

It's a reply typical of someone not directly involved in the problem domain. Unfortunately so few people are ... chicken an egg situation: nobody uses Java for this stuff because it's such a pain and a lot slower than C, so there are no people with a problem...

...I am corresponding with Peter von der Ahé, who I believe is a VM engineer, on the subject. I will CC Jeff K. in on it because he understands what the RFE is about.

Since I'm far too lazy to maintain a proper website at the moment...I wrote an impromptu monologue the other week on structs, at far too late/early in the morning. Might be crap. Seemed to make sense at the time .

Gah. Don't know what happened - probably I had it open on another window too, and closed the windows in wrong order after I'd made page 2 visible, causing it to re-hide the second page (makes it private). Fixed now.

Horrible website aside, that was getting quite interesting to read but then seemed to stop only halfway though and without actually making any kind of point.

Yeah, I just noticed that too. I have a horrible feeling I just got bitten by a POST form limit on a J2EE server. Grr.

PS: horrible website == why I said I was being lazy. Not my site, just a place where I can conveniently login and edit a webpage on the fly through my browser. It's not intended to be used for this, but I'm having server + domain issues I haven't got time to fix right now

Not strictly true, there will always be at least one object, but my idea is to have it able to slide around inside a ByteBuffer like a window. It's not like the "lightweight objects" proposals that IBM and some mathematical fraternities have been espousing.

It will speed up LWJGL a fair amount if you do a lot of vertex pushing - behind fillrate, geometry transfer and processing is the other big bottleneck in 3D. I suspect scenegraphs like Xith and jME will benefit by a few fps with structs - and there's a good chance there are some opportunities to save a few megs of RAM in object overhead too. Not to mention the code will be greatly simplified.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org