it finished well. fread: 1 end of m_fread: 1 start of put_token: m_size=256 m_cnt_tkn=3 put_token:token=byte end of put_token: g000 token=byte g000 i: 1 end of m_fread: 1 fread: 1 end of m_fread: 1 start of put_token: m_size=256 m_cnt_tkn=…

20191107 We set max 10 and compiled and displayed 1850604599 and stopped which was array morization of class. We've already solved that problem. end of m_fread: 1 fread: 1 end of m_fread: 1 end of m_fread: 1 fread: 1 end of m_fread: 1 end …

We could extract first funcyion line. it would be analyzed as function. // prototype: // // // // // int aToken::block_to_function_end( int *index , int file_end, FILE *fp) { char dummy[256]; char* a_token = nullptr; int breakable = 0; int…

We don't think about the below: // prototype: // // // // // int aToken::block_to_function_end( int *index , int file_end, FILE *fp) { char dummy[256]; char* a_token = nullptr; // function start which is '{'. // function end which is '}'. …

int aToken::found_type( char* p_token ) { if ( m_compare( p_token, "void") == 1 ) { err_msg_006("p_token: %s\r\n", p_token ); //exit(-1); return 1; } else if ( m_compare( p_token, "int") == 1 ) { err_msg_006("p_token: %s\r\n", p_token ); e…

20191102 We could find void, so, we are going to analyze function part. We added class aToken function private "int found_type( char* p_token )". int aToken::found_type( char* p_token ) { if ( m_compare( p_token, "void") == 1 ) { err_msg_0…

Program finished normally.3000 was the limit number of persing. github.com Program finished normally. 3000 was the limit number of persing. --- start of put_token: m_size=256 m_cnt_tkn=0 put_token:token=p end of put_token: g000 token=p end…

it doesn't print it well. // // // // // void print_memories () { int a = level_error_msg; level_error_msg = 6; for ( int i=0; i

We changed error message functions: err_msg_002 -> err_msg_006. We could print it well. --- start function: array_count: start function: array_count: start function: array_count: start function: array_count: start function: array_count: st…

willinglytranslate.blogspot.com

1stWe touched files and then, we realised, we cannot save before sompilations the time when file is accurate.When we saved the file if the files were changed.So, we give up so, we giveup fighting this. 2ndIn frame works give us unchanging …

Which information you need is your understanding somthing.Now, we think, inside file was changed before operation.Hardly, we could not proof that: The proofment we need, 1. file name 2. file size of 1 3. All of File So, if we checked the a…

the below was compiled mistaken cuase of my fault. their messages in not ensured. I beleive we could compile the source code even though we don't touch it after first compiling it. https://github.com/WaitrudWeber/source_zip/blob/master/ana…

It doesn't print next Analyzer::parse: starts. // // // // // int Analyzer::parse ( char* filename ) { FILE *fp; aToken *iToken = nullptr; char *parse_token; int previous_index = 0; char dummy[256]; char* a_token; int mode_token = 0; iToke…

we could have recognised well prints of it. WM_MESSG 003: 20 *(p_evt->uMsg):20 wButtonController::Process: 20 / 15<-WM_PAINT wParam 1493243959 lParam 0 this->event->uMsg:6551900 *(this->event->uMsg)=20 Called: InvalidateRect( this->event->…

Called: InvalidateRect( this->event->hWnd, NULL, TRUE) WM_MESSG 004: 20 *(p_evt->uMsg):20 uMsg:20 p_evt->uMsg: 6551900 &uMsg: 6551900 WM_PAINT 002: 15 *(p_evt->uMsg):20 uMsg: 15 WM_MESSG 003: 15 *(p_evt->uMsg):20 wButtonController::Process…

We could print messages. Assembling the below: void err_msg_004(const char *fmt, ...); err_doit(0, 0, fmt, ap); -------------- Called: InvalidateRect( this->event->hWnd, NULL, TRUE)WM_MESSG 004: 20 *(p_evt->uMsg):20 uMsg:20 p_evt->uMsg: 65…

We could change our imagine and throw out and give up "just a way". We've already put Sleep and tried it. #include // // // // // char* err_msg_002(const char *fmt, ...) { static char* result; static va_list ap; Sleep(1000); if ( set_level…

va_start(ap, fmt); has the character 1. copying ap nside their function. We hardly use va_start inside local function from usage. However, we could use printf well. And, binary is banary in even Library.

We think the program cannot memory well first. We wonder if the program has memorization eroor or not. There is something usage in windows programming: 1. Use static as local param. 2. Use mallloc if you can. 3. Use sleep. And then, we cou…

wButtonController::Process: 20 / 15<-WM_PAINT wParam -2097082227 lParam 0 this->event->uMsg:6551900 *(this->event->uMsg)=20 Called: InvalidateRect( this->event->hWnd, NULL, TRUE) WM_MESSG 004: 20 *(p_evt->uMsg):20 uMsg:20 p_evt->uMsg: 6551…

We could say print error and compiled error. github.com I remained this as error even though I could not solve this problem.

iToken->free_main_token (); Always, this error was obvious, but we don't know how we modify the error. And, block was still remained.

Analyzed #include and #defined and else but which is #define tipically how could we mistake. // // // // // int Analyzer::parse ( char* filename ) { FILE *fp; aToken *iToken = nullptr; char *parse_token; int previous_index = 0; char dummy[…

The answer is how we might memorize, but only one of reasons. Use of static memories avoid so many troubles in windows programs and which, ensures a lot of moves and processes not in details. We'd rather like err_msg_002 customized from er…

int Analyzer::parse ( char* filename ) { printf("Analyzer::parse\r\n" ); return 0; } wButtonController::Process: 20 / 15<-WM_PAINT wParam 1275139515 lParam 0 this->event->uMsg:6551900 *(this->event->uMsg)=20 Called: InvalidateRect( this->e…

it didn't cae here. int Analyzer::parse ( char* filename ) { err_msg("Analyzer::parse\r\n" ); return 0; } default: WM_MESSG 004: 256 *(p_evt->uMsg):256 uMsg:256 p_evt->uMsg: 6552728 &uMsg: 6552728 WM_MESSG 000: hWnd 3082844: uMsg 258: wPar…

it didnt work well, and previously did work at least. // Qualified: 20190921: found #define: // // // // // char* aToken::getToken( FILE *fp, int *index, int *file_end ) { static char dummy[256]; int breakable = 0; int mode_token = 0; int …

We cound not move err_msg or error. We don't touch any other functions and they well know how people mistake. I suppose, err_msg does work. // // // // // int Analyzer::parse ( char* filename ) { FILE *fp; aToken *iToken = nullptr; char *p…

change printf to self-created function, which would bring us something for debugging so that we could set levels for it even after starts of system. // // // // // int Analyzer::parse ( char* filename ) { FILE *fp; aToken *iToken = nullptr…