because we need it on our own server I guess

You can host it on local machine

Hi! Creating a simple QT project, that reads a dictionary.txt. Don't know how to include path to dictionary.txt in project. Created subfolder /res put dictionary.txt there added the folder to .pro file so that folder and it contend show up in tree. However compiler does't see dictionary.txt unless i provide full path

Hi! Creating a simple QT project, that reads a dictionary.txt. Don't know how to include path to dictionary.txt in project. Created subfolder /res put dictionary.txt there added the folder to .pro file so that folder and it contend show up in tree. However compiler does't see dictionary.txt unless i provide full path

dont i need the length to know when to end the loop?

For CS? Everything there is on internet, every bit of information is important, but if you ask specifically about something then there is a chance someone might recommend something.

What do i need to learn first

Start programming like newbie?..

What do i need to learn first

C++

I wanna start programming professionally

C++

Yeah learn architecture and assembly programming first, that'll be easier 😅

Yes... But I would suggest easier lang

Yeah learn architecture and assembly programming first, that'll be easier 😅

Assembly lang. is not that useful...

For counter strike

Counter Strike?

Assembly lang. is not that useful...

Assembly lang. is not that useful...

Cs = ©ounter $trike

What do you mean by that? Maybe I should google it.

spoiler: you can't

Its. Like... First letters

Oh it's a game... okay.

Actually Assembly language is not useful but originally it gave an idea how the computer really worked, the original DOS based C programs are opitimized if you know how computers really work.

That is computer architecture, not assembly language as it is. Studying CPU command codes and command execution is good. Studying how to , say, develop Excel or MS Word in Asm -- no, not useful

if you program c, have fun actually understanding whats going on while you have 0 clue about asm

It's just common prejudice.

if you program c, have fun actually understanding whats going on while you have 0 clue about asm

Assembler as a bad thing to learn because it is bound to the particular CPU type and computer architecture. If you study ALL existing architectures and their machine codes / assemblers this is useful but not needed for most developers. If you study only one (like Intel) this gives you impression that all machines run exactly like this one. This may me harmful. If you take into account the fact that assembly languages are very rarely used in practice, I would not recommend studying asm at all.

dumb example, you have this piece of code, try to explain why this does not work without referencing anything on the lower level int32_t *ipAdd(int32_t iValueA, int32_t iValueB) { int32_t iResult = iValueA + iValueB; return &iResult; }

Basic assembler is always useful

Basic assembler is always useful

Yes, always useful as no knowledge is useless. But not necessary at all

Does anyone know any good resources for learning to prevent memory and pointer based errors?

Does anyone know any good resources for learning to prevent memory and pointer based errors?

Does anyone know any good resources for learning to prevent memory and pointer based errors?

Does anyone know any good resources for learning to prevent memory and pointer based errors?

Does anyone know any good resources for learning to prevent memory and pointer based errors?

Here is the simple code #include <stdio.h> #include <stdlib.h> /* required for the malloc and free functions */ int main() { int number; int *ptr; int i; printf("How many ints would you like store? "); scanf("%d", &number); ptr=malloc(number*sizeof(int)); /* allocate memory */ if(ptr!=NULL) { for(i=0 ; i<number ; i++) { *(ptr+i) = i; } for(i=number ; i>0 ; i--) { printf("%d\n", *(ptr+(i-1))); /* print out in reverse order */ } free(ptr); /* free allocated memory */ return 0; } else { printf("\nMemory allocation failed - not enough memory.\n"); return 1; } }

The best way to avoid most mistakes is by using smart pointers. Also, good static analyzers (clang-tidy) and profiling tools (valgrind) can help you prevent most memory bugs

Will I appear impolite if I just jump in and ask some questions right away ? :)

What do i need to learn first

Here is the simple code #include <stdio.h> #include <stdlib.h> /* required for the malloc and free functions */ int main() { int number; int *ptr; int i; printf("How many ints would you like store? "); scanf("%d", &number); ptr=malloc(number*sizeof(int)); /* allocate memory */ if(ptr!=NULL) { for(i=0 ; i<number ; i++) { *(ptr+i) = i; } for(i=number ; i>0 ; i--) { printf("%d\n", *(ptr+(i-1))); /* print out in reverse order */ } free(ptr); /* free allocated memory */ return 0; } else { printf("\nMemory allocation failed - not enough memory.\n"); return 1; } }

it seems that unlike function bool variable won't change as parts of expression change for example ``` word = data; xword=data bool compare=word==xword //true word=aata xword=data compare (?) ``

8989 members 🥳

Ya program write hai

What?

It's a pun

it stops compiling as soon as binaries are getting larger than 640k

Is this indian?

No