🚀 go-pugleaf

On Sunday, April 30, 2017 at 12:49:15 PM UTC+2, (fir) wrote:
> W dniu niedziela, 30 kwietnia 2017 10:44:50 UTC+2 użytkownik (fir) napisał:
> > W dniu niedziela, 30 kwietnia 2017 01:18:19 UTC+2 użytkownik Matt D. napisał:
> > > On 4/29/2017 14:46, (fir) wrote:
> > > > if you got exe or dll the most important sections are .code .data .const and .bss
> > > >
> > > >  need a simple console program that show the size of the code
> > > > (in bytes and also in percent) in given .exe .dll [also sieze of consts and initialised data, yet size of static arrays]
> > > 
> > > Tools:
> > > GNU Size: https://sourceware.org/binutils/docs/binutils/size.html
> > > PE Insider: http://cerbero.io/peinsider/
> > > 
> > > GNU Size Examples:
> > > http://www.geeksforgeeks.org/memory-layout-of-c-program/
> > > ttp://cs-fundamentals.com/c-programming/memory-layout-of-c-program-code-data-segments.php#size-of-code-data-bss-segments
> > > 
> > > See also Ange Albertini's work:
> > > http://i.imgur.com/tnUca.jpg
> > > https://speakerdeck.com/ange/workshop-exploring-the-portable-executable-format
> > > https://github.com/corkami/docs/blob/master/PE/PE.md
> > > https://speakerdeck.com/ange/x86-and-pe
> > > https://speakerdeck.com/ange/byte-ing-the-pe-that-fails-you
> > > https://speakerdeck.com/ange/booklet-elf101-a-linux-executable-walkthrough
> > > 
> > > Best,
> > > 
> > > Matt
> > 
> > ok, tnx moze sie przyda.. niby program napisany na razie a grzebanie w tym pe jest nudne ale jak ktos jest nieskopoziomowym programista windows to nieststy trzeba chyba znac
> 
> ps przy okazji skrobnalem disklaimer dlaczego czasem moj kod jest "enough good"
> 
> (ps my code posted is badly shaped i know, but it is becouse i do not code edge cases firstly also do not 
> shape code stylistically firstly (just to spare as 
> much energy i can) - anyway one must establish some level on which one think "this code is ENOUGH good" 
> and it is not excluded that setting this level lower 
> is better than setting it higher (i know using structs and do some edge case checking, reformating names and 
> shape etc is in fact better.. but form other point of view go worse is better - so i write this disclimer 
> to say that for sure i know thic coede i post could 
> look better but i also deny to tace comments on this as i code how i code for some practical purpose and dont like to meet morons with their stupid comments like your code is ugly ;c hope im understood) 
> 
> pisze to bo nie chce mi sie gadac z rozmaitymi debilami ktorzy pewnie zawsze pala sie by wypominac "bledy w kodzie " czy "zly wyglad" o czym nie mam zamiaru ostatnio  dyskutowac

My solution:

#include <stdio.h>
#include <iostream>

int main()
{

    FILE* file = fopen("file.txt", "r+w");

    fseek(file, 0, SEEK_END);

    unsigned long long space_count = 0;
    unsigned long long chars_count = 0;
    unsigned long long lines_count = 0;
    unsigned long long all_count = 0;

    char* ch = new char[1];

    while(!feof(file))
    {
        fread(ch, 1, 1, file)

        ++all_count;

        if(ch == 32) //space
            ++space_count;
        else if(ch == 13) //endline
            ++lines_count;
        else
            ++chars_count;
    }

    std::count << "spaces: " << space_count << std::endl;
    std::count << "chars: " << chars_count << std::endl;
    std::count << "lines: " << lines_count << std::endl;
    std::count << "all_count: " << all_count << std::endl;

}