The problem when using a array as a parameter, the array will be a pointer(not a array):Looking at the code and it crashes there, looks more you are sending a constant string or a unallocated pointer, as parameter.

Yeah i got rid of the char array, here is updated version of whole source. Main reason for program is to translate braille to readable english. Mind you it's not fully done yet. But I got past the seg fault and a littler further.

LoGiCaL__ wrote:Yeah i got rid of the char array, here is updated version of whole source. Main reason for program is to translate braille to readable english. Mind you it's not fully done yet. But I got past the seg fault and a littler further.

Here is updated source:

I'm curious to the purpose of this program... As far as I'm concerned, braille is read by the fingers of blind people. Actually FEELING what they are reading. Which would make it really difficult to implement such a system, dynamically, and on the computer. Seeing as the only tactile response a computer will ever give out is the signal from your keyboard or mouse to their respective drivers...

On-topic: I would comment on your code, but after coding in C for ~2 now, I've all but forgotten anything related to OOP. Lo siento amigo.

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -Rick Cook

centip3de wrote:Which would make it really difficult to implement such a system, dynamically, and on the computer..

That's what inspired me to write it. The actual site is helenkellersim.com . Check the source code when you get to the page.

I was trying to say if you sat a real blind person down at a computer and asked them to tell you what was on the screen, no matter how advanced the program was, they couldn't do it. The only way the could do that (with braille) is for there to be dynamically changing hardware, which is insanely hard. That was what I was trying to say.

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -Rick Cook

Yeah, I realize there is basically no use unless people who can see want to learn braille. However, it does seem like a good way to pass messages digitally. What I mean is that it could just be another layer in some already encrypted message.

LoGiCaL__ wrote:Yeah, I realize there is basically no use unless people who can see want to learn braille. However, it does seem like a good way to pass messages digitally. What I mean is that it could just be another layer in some already encrypted message.

Possibly... But from what I understand, braille uses multiple lines to symbolize different things. For instance a square of bumps could mean one thing, while a triangle another, which would seem to make translations between the two difficult and inefficient. I honestly don't know much about braille, or encryption in all honesty, so take what I say with an extremely large grain of salt.

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -Rick Cook

Well, I finally got this program in working order. There are still some things I would like to work on to make it work correctly. For now though it's good. Some things I would like to work on are reducing line count some. As of right now in the .txt file it takes the braille from, at the end of each line you have to manually make sure it has one space after last char and then goes to the next line for all the lines. I want to build this into the program just in case of different copy and pastes.