Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c    |    Meh, in C you gotta define EVERYTHING    |    243,242 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 242,423 of 243,242    |
|    wij to All    |
|    Re: Updated P!=NP proof (1/2)    |
|    11 Dec 25 23:43:18    |
   
   From: wyniijj5@gmail.com   
      
   The script of proof is formal enough to submit to professional institute, I   
   think.   
   Anything unclear or defect?   
      
   The following is form https://sourceforge.net/projects/cscall/fi   
   es/MisFiles/PNP-proof-en.txt/download   
      
   ----------------------------------------------------------------   
   ---------------   
   Algorithmic Problem::= A computer problem in which the computational steps are   
   a   
    function of the problem statement's length (size). This problem can be   
    described asymptotically as the relationship between the problem size and   
    the computational steps.   
      
   Polynomial-time procedure (or Ptime procedure)::= O(P) number of consecutive,   
    fixed-sized basic operations (because the procedure is a deterministic   
    process, it is sometimes called a "function" or "operation"). Therefore, as   
    defined by O(P), O(P) number of Ptime procedures executed consecutively can   
    also be considered as a single Ptime procedure.   
      
   Reduction::= The algorithm for computation problem A can be transformed into   
    computation problem B by a Ptime procedure, denoted as A≤B (because the   
    Ptime transformation itself includes the computation of problem A, any two   
    Ptime problems can be reduced to each other).   
      
   ANP::= {q| q is a statement of a decision problem that a computer can solve in   
    O(2^|q|) steps using the following fnp algorithmic template. q contains a   
    certification dataset C, card(C)<=O(2^|q|), and a Ptime verification   
    function v:C->{true,false}. If ∃c,v(c)=true, then the answer to problem   
   q is   
    true; otherwise, it is false.}   
      
    // begin_certificate is a Ptime function that retrieves the first   
    // Certificate element from the problem statement q. If this element does   
    // not exist, it returns a unique and virtual EndC element.   
    Certificate begin_certificate(Problem q);   
      
    // end_certificate is a Ptime function that retrieves the element EndC from   
    // the problem statement q.   
    Certificate end_certificate(Problem q);   
      
    // next_certificate is a Ptime function that retrieves the next element of   
    // c from the certification dataset C. If this element does not exist,   
    // return the EndC element.   
    Certificate next_certificate(Problem q, Certificate c);   
      
    // v is a Ptime function. v(c)==true if c is the element expected by the   
    // problem.   
    bool v(Certificate c);   
      
    bool fnp(Problem q) {   
    Certificate c, begin, end; // Declare the certification data variable   
    begin= begin_certificate(q); // begin is the first certification data   
    end= end_certificate(q); // end is the false data EndC used to   
    // indicate the end.   
    for(c = begin; c != end;   
    c = next_certificate(q, c)) { // At most O(2^|q|) steps.   
    // next_certificate(c) is a Ptime   
    // function to get the next   
    // certification data of c   
    if(v(c) == true) return true; // v: C->{true, false} is a polynomial   
    // time verification function.   
    }   
    return false;   
    }   
      
    Since a continuous O(P) number of Ptime functions (or instructions) can be   
    combined into a single Ptime function, at roughly this complexity analysis,   
    any Ptime function can be added, deleted, merged/split in the algorithm   
    steps without affecting the algorithm's complexity. Perhaps in the end,   
   only   
    the number of decision branches needs to be considered.   
      
    An ANP problem q can be expressed as q
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca