next topic »

[on:]

I have a couple of questions:

1. operator[](int) is not defined -> is this normal?
2. Say, I have a library and a sketch. What I would like to do (and should be possible, this is C++) is:
   in the sketch:

Code:

#define XYZ
#include <library.h>

   in the library:

Code:

#ifdef XYZ

   -> why doesn't this work?

[Reply #1 on:]

Although you have those statements in that order in your main code, are you sure that is the order in which the compiler uses them ?

[Reply #2 on:]

How to use this forum

Read this before posting a programming question


Where is your code?

[Reply #3 on:]

I have a couple of questions:

1. operator[](int) is not defined -> is this normal?
2. Say, I have a library and a sketch. What I would like to do (and should be possible, this is C++) is:
   in the sketch:

Code:

#define XYZ
#include <library.h>

   in the library:

Code:

#ifdef XYZ

   -> why doesn't this work?

Defining something in the sketch does not make it defined in the library. That is a different compilation unit.

[Reply #4 on:]

Ok. I thought the arduino IDE made one big compilation unit from the whole thing. My mistake.

[Reply #5 on:]

Your sketch (the .ino file) becomes a compilation unit. The library is separate. Passing things to the library is only really possible by sending things via (say) the constructor (if you are using a class).

[Reply #6 on:]

Thanks, I stand corrected.

[Reply #7 on:]

Nick:

Where is your code?

Code:

void setup() {
}

void loop() {
  int* test = new int[123];
}

result:

Code:

sketch_feb24b.cpp.o: In function `loop':
/usr/local/home/tomas/arduino-1.0.3/sketch_feb24b.ino:5: undefined reference to `operator new[](unsigned int)'

[Reply #8 on:]

Never mind. I figured it out.
But still, I find it a bit strange (coming from a C++ background) to define:

Code:

void * operator new(size_t)

and not

Code:

void* operator new[](size_t)

I guess I'll add new[] and delete[] myself.

[Reply #9 on:]

Never mind. I figured it out.
But still, I find it a bit strange (coming from a C++ background) to define:

Code:

void * operator new(size_t)

and not

Code:

void* operator new[](size_t)

I guess I'll add new[] and delete[] myself.

Don't forget that you only have a couple of KB of RAM to play with, so any dynamic memory allocation at all is a Really Bad Idea™

You should shy away from it whenever possible, and stick to using statically defined objects and variables.

Even on the nice powerful PIC microcontrollers I work with that have 128KB of RAM I don't like to use dynamic memory allocation if it can be avoided...

[Reply #10 on:]

I guess I'll add new[] and delete[] myself.

For some reason they added new and delete but not new[] and delete[].

I think I have an outstanding bug report about that.

http://code.google.com/p/arduino/issues/detail?id=883

[Reply #11 on:]

Don't forget that you only have a couple of KB of RAM to play with, so any dynamic memory allocation at all is a Really Bad Idea™

Yes I understand. I just wanted to allocate 14 bytes, once, and delete them a few seconds later... I just think it's strange to get a compilation error for new[]. (I'm very new to microcontroller development, and finding out things like this every day)