Page 2 of 2

Re: software compatibility

Posted: 09 Jan 2013, 17:54
by mattallen37
If it's all local to one NXT, then use a global array, instead of copying it all the time. It can help significantly.

Re: software compatibility

Posted: 09 Jan 2013, 17:58
by HaWe
if it's possible, yes, but if it's not possible, no. I am talking of the no's.
And pointers also are rational for dynamic memory allocation, and sort algorithms for linked lists, and many other thngs.

Better don't let's start again arguing off-topic.

But if you want to argue, BRING IT!
I GOT MY CAPSLOCK ON!! :twisted:
Into a room full of Java and C programmers, shout out loud:
"POINTERS?? WHO NEEDS POINTERS !?!"
And then run for your life.
:twisted:

Re: software compatibility

Posted: 09 Jan 2013, 18:56
by mightor
If you don't stop it with the spoiler tag, I will simply remove it.

= Xander

Re: software compatibility

Posted: 09 Jan 2013, 20:01
by HaWe
It was only because I was forced to off-topic statements. So it doesn't rip the thread so much.
(I see no interdict to do that in the forum rules.)
On the other hand, do what you can't leave, it's ok for me.

Re: software compatibility

Posted: 10 Jan 2013, 14:03
by hassenplug
doc - I'm not sure the discussion about software & pointers is "off topic" for a thread entitled "software compatibility" in the "Mindstorms Software" forum.

The spoiler tags are more annoying than posting off-topic items.

I'm going to ask that you put a little effort into being extra considerate for a while, and playing well with others. Call it a favor to me.

Steve

Re: software compatibility

Posted: 10 Jan 2013, 17:00
by HaWe
I found it OT by myself even because I myself mentioned that the pointer thing actually was OT in that moment -
because we didn't ever have pointers so far for NXC, and so it's no compatibility issue.

It was actually only an extra feature of native C compilers additionally to speed and math and statitistic libraries which are usually already all-in, that was the point we
initially have been discussing.
Similar was the issue about Metthew's proposal for a possible workaround for certain circumstances when pointers are missing.

In order not to bore those who are only interested in compatibitlity to current software (e.g., NXC) but not interested in the recent pointer discussion I decided to hide this aspect for those people who might not be interested in it at all and on the other hand make it optionally visual for all the others who might be interested in this OT border area nevertheless.

I thought it was helpful and rational to make it this way. But of course I can let it be.
If you don't like spoilers why not cancel it completely?

ps, edit:
if Xander had posted more friendly, I would have certainly responded in a different style.