Wait a minute it just dawned on me what you are doing. You are creating reference for jpeg compression algorithm which means you are working in bitmap already.

Wouldn't it be easier to bitmap it then recompress it back into the jpeg using the same algorithm format?

There are also a lot of techniques in which you may pass processing to one of a set of functions by means of a switch statement. If you have an array of function pointers you could simply pass to that offset in your array of pointers. There's also ease of adding a new function to that list where all you need to do is add an extra switch statement and the pointer into the array.

Duh yup, When you simplify, it's painfully clear as A* = A* to new object as: NonLeafTrieNode **ptrs = (NonLeafTrieNode*) new object; I think you know what I'm trying to say rather that ptrs[x]. That this pointer -> just kept saying "I'm in a mystery object" which doesn't matter. Err. Hate it when that happens. :doh: -- modified at 1:50 Tuesday 20th September, 2005 :suss: Ya know this dumb thing kept buggin me so I went to my compiler and guess what? It worked! But it still kept bugging me since this is not a normal thing I would try so I thought outside of the obvious why havn't I tried this just for the stupidity of it. Then I thought. :cool: class A{}; class B{ public: int j; }; int main (int argc, char* argv[]){ A* newptr = (A*) new B; newptr->j=5; return 0; } ;P Ya, I was a bit suprised when it let me do the initial A* newptr = (A*) new B; because it just doesn't feel right. Guess I'm too methodical.

Hi Rich, I'm just pondering how his compiler is allowing the cross reference from one object pointer to the other unless p-> is of void that, yes just points to raw memory space by which he will need to not only delete the pointer but reclaim the memory space as well or get a memory leak. :doh:

:confused: I can't see that it would with what you have displayed because there's alot missing to a completed and running example. What exactly is p-> ? If p is a member of a child class of both or a trianglular reference to a void parent member not listed, I could see where your compiler may confused. Either way, it looks like you are opening up to a memory leak.

So you're trying to ring my bell because now you are creating ambigious function pointers.

You need something to parse your input with like a char str and extract your numerical into a double. int doesn't do decimal so how do you know if a decimal is in your input? It's a text file input so it's automatically a char going in. atof() and isalnum() would be my first thought or get out your ASCII table if you want to build your own smarter atof() to parse your entire input line at a time. I don't know of anyone that wants to just hand you an answer to copy. Remember the basic purpose of a template it to reduce redundant code differing only in parameter type, allowing the same call with different types. But then again maybe I'm not understanding what you are doing, like are you pulling the entire input file into a buffer or are you grabing input by keyword, space, line ??

Hello All, :~ Say, is there anything akin to a family tree app for classes and their inheirited children, typedef class template wanta be's, etc.? Flippping back and forth between declarations and definitions, tracking back 4-12 levels of header files leaves me wondering what it was I trying to figure out to begin with. :confused: There's got to be a better way. So is there any open source that will show visual relationships? Even a plain text outline would be better than my strained brain cells. Or do I have to take yet another deviation from my destination and write one myself? X| Thnks