maybe its just been too long since i did heavy duty C++ programming but I thought for sure that any function retained all objects, primitive or not, until that function or method was done and was removed from the stack. If I have a function pointer doesn’t this pointer stay alive for as long as its parent function lives? sorry for the confusion here.
also since you have already declared your typedef as ^ArrayEnumeratedBlock…why would need to repeat that argument list down within the block?
shouldn’t you be able to do:
- since devowelizer was declared now as a type and it should i would think be able to know about the types arguments. No biggie just brainstorming here. Just makes it a bit more confusing I think.
Lastly, why wouldn’t I, maybe by nature, just choose to declare and implement a method that would be passed a message(a string) and use that method to remove all the vowels? perhaps there would be a file with tons of words or sentences and i would use that loop to call this method to return back the string without the vowels or perhaps write the new strings to a file. This way i could reuse this method down the road in another application without having to worry about where the string comes from - i.e. code reuse. Again sorry for the many questions… just trying to get my head around it all.