Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wru5k-0003m3-9g for bitcoin-development@lists.sourceforge.net; Tue, 03 Jun 2014 19:09:48 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of yahoo.com designates 98.138.229.32 as permitted sender) client-ip=98.138.229.32; envelope-from=rdwnj@yahoo.com; helo=nm39.bullet.mail.ne1.yahoo.com; Received: from nm39.bullet.mail.ne1.yahoo.com ([98.138.229.32]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Wru5i-0004Ry-IK for bitcoin-development@lists.sourceforge.net; Tue, 03 Jun 2014 19:09:48 +0000 Received: from [127.0.0.1] by nm39.bullet.mail.ne1.yahoo.com with NNFMP; 03 Jun 2014 19:09:41 -0000 Received: from [98.138.100.103] by nm39.bullet.mail.ne1.yahoo.com with NNFMP; 03 Jun 2014 19:07:01 -0000 Received: from [98.138.101.181] by tm102.bullet.mail.ne1.yahoo.com with NNFMP; 03 Jun 2014 19:07:01 -0000 Received: from [127.0.0.1] by omp1092.mail.ne1.yahoo.com with NNFMP; 03 Jun 2014 19:07:01 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 660414.86947.bm@omp1092.mail.ne1.yahoo.com Received: (qmail 97558 invoked by uid 60001); 3 Jun 2014 19:07:01 -0000 X-YMail-OSG: OeLFJjQVM1lzUWQfIrNjBGnpfcvF09ajum77HNu0HxitHK8 6JhqaLZB6pmmK9gwbmQica1uaX2sn_omVuW3Q6SJv.2WA45XMoXDdYWWSsYD bloEizC1bgVtFSMGUW0aAVQvbLU4xHNyVMI6ddvZXUIsBhTfTfKdXJAYQjZ7 f3SmNygOaxQLvJDLxEPqUQ89GDw7OynXFmhlV4vFkw4zQGCDeLHY3.28iXRK 1ZgsijiqveGhC5OgXwkM_vCZVVFyf7ZGolOR7F74BmceNJKfh4JrJpzI8mCB aueZSnP8aWkKDXgSjRftaA7dpM_6OD8jYH2ihB2QxUpn1eeAnsX3Mihhj3CH 5VnIb79puiGH6Z7gFm2_KEFj9REg5M1N7FJHAne_hmUZ852i9I99aE.nrbaY Yf6wmCnEm443vqm2TfK_U6JCoJ69z29ZJ9I9fOxF.UY67dkqNeJjpHO45SS_ dm9ot2AXfoJx.lZZQWsaiFkvaEbyS26MYBuyvj5WG1oxV9D4YepRO1d5xqcC yMLity04mCVG1EE.r5D6UeGLokEBL3jZrBYuFWheJHa6o.Bq7gRTkyXDcQWO hQxBDDJnqKWT1phaiRAkj32J4P9ZwoXPNy6srFNfKliH4tRRJxWXIYOuPeMC vy2RF5RXAKE1p7JiuUNaI.xgXZeW37kLVxG5qfIob_rMxh9b2XVsyKKXL2gN lvs5pp_2HoftIvxCZk.7RKJNIvj2_rXcYRz0x9zhVYr8aN5x1wR5S.VyZ2vc kSJvzo0ZdGDr0fiiaWugjpPpS_F2ExLn.mN2eJf5GpemWb5xsPnsgbrIzath zLYPF6tA3ps.3B_0CudHwAo6jIDJ.g5kKL7B4uIm1.JTQ.Ym89mPIIfYGEum MNdHu66LcfnrhsOdLtAQXUgvc5to0RkGgl.cKngrzbSMIuhYqzIaB28cJ8Qg MUjHqhJj81pHVC9M6Z11OD7DnCq1q_JPGMOzXLvZt2x8R.AdgGzEqotGaEJJ q2RII4VODthTj8ewfdRQPet6tO15oWWtvD8UmlSQ3hKrwwLUK7lx7HmF2Rsh rWGSet0VqKDYflSoyZ_JrF16fSARYAPTU71jl6CqmztYtnjyolYmV9aNw.gr 66OUMThVpJ69hvpbVuKmMeg-- Received: from [24.46.202.44] by web124505.mail.ne1.yahoo.com via HTTP; Tue, 03 Jun 2014 12:07:01 PDT X-Rocket-MIMEInfo: 002.001, SGVsbG8KCldoYXQgaXMgdGhlIGlzc3VlIHdpdGggdGhlIEJpdGNvaW4gY29kZSBmb3IgMC45Lnggd2l0aCByZWdhcmQgdG8gYXNzZXJ0aW9ucyB0aGF0IGlzbid0IGluIDAuOC42IG9yIHByZXZpb3VzIHJlbGVhc2VzPwoKb24gQXByaWwgMTh0aCwgSSBvZmZlcmVkIAoKaHR0cHM6Ly9naXRodWIuY29tL2JjNC1vbGQtYy1jb2Rlci9iaXRjb2luL2NvbW1pdC9mMGQyMjFlNTZhMTI5NDdiNjdiOWM4ZjQzY2M1ODMyYjY2NTA1MmM4IAoKdGhpcyBjb21taXQgYW5kIGNvZGUgd2l0aCBhbGwgc2lkZSBlZmZlY3RzIHIBMAEBAQE- X-Mailer: YahooMailWebService/0.8.188.663 References: Message-ID: <1401822421.27942.YahooMailNeo@web124505.mail.ne1.yahoo.com> Date: Tue, 3 Jun 2014 12:07:01 -0700 (PDT) From: Ron To: "bitcoin-development@lists.sourceforge.net" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-604106506-1248391825-1401822421=:27942" X-Spam-Score: 1.4 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.229.32 listed in list.dnswl.org] 1.0 HK_RANDOM_REPLYTO Reply-To username looks random 1.0 HK_RANDOM_FROM From username looks random -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.6 HK_RANDOM_ENVFROM Envelope sender username looks random 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rdwnj[at]yahoo.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wru5i-0004Ry-IK Subject: [Bitcoin-development] # error "Bitcoin cannot be compiled without assertions." <<< List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 19:09:48 -0000 ---604106506-1248391825-1401822421=:27942 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hello=0A=0AWhat is the issue with the Bitcoin code for 0.9.x with regard to= assertions that isn't in 0.8.6 or previous releases?=0A=0Aon April 18th, I= offered =0A=0Ahttps://github.com/bc4-old-c-coder/bitcoin/commit/f0d221e56a= 12947b67b9c8f43cc5832b665052c8 =0A=0Athis commit and code with all side eff= ects removed from the assertions.=0A=0A=0AThen on the 28th,=0A=0Ahttps://gi= thub.com/bc4-old-c-coder/bitcoin/tree/0.8.6 =0A=0Athis code with unit tests= working.=0A=0AAnd if that isn't enough, I did a video series on building B= itcoind.exe and the static libraries (on MSVC++) all in NDEBUG (release) mo= de.=0A=0ASee=0Ahttps://www.youtube.com/playlist?list=3DPLFnWb0ttBBMLyUuniLp= 3PJ5Mn4tVUlliZ=A0 =0ANotice that the NDEBUG release mode is featured, and I= even run it!=0A=0ALastly what does that say about building Bitcoin-qt in r= elease mode?=A0 Should one or not??=0A=0AThere is also a video on building = an alternate coin-qt.exe in release mode (gcc version) and running it!=A0 S= ee =0Ahttps://www.youtube.com/watch?v=3DC8GvHpjbAnM =0A=0A=0A=A0=0A=0A=0Aas= sert() should have no side effects, that is the problem.=0A=0ASee=0Ahttp://= books.google.com/books?id=3DL5ZbzVnpkXAC&pg=3DPA72&lpg=3DPA72&dq=3DGotcha+%= 2328+Side+Effects&source=3Dbl&ots=3DRn15TlPmje&sig=3DtymHqta0aSANwaM2GaXC-1= Di_tk&hl=3Den&sa=3DX&ei=3DuVKNU47fCcvTsAT6goHIBA&ved=3D0CCAQ6AEwAA#v=3Donep= age&q=3DGotcha%20%2328%20Side%20Effects&f=3Dfalse=0A=0Aa=0A great book, BTW= .=A0 Everyone who thinks they know what they are doing =0Awhen they write C= ++ should read this book!=A0 They will realize that they =0Adon't know Jack= =0A=0AWhy weren't these and all the other examples of amateur, i.e., non-p= rofessional, software fixed way back in version 0.3.0 in 2010, before any m= ore releases were done?=A0 And why were these and other sub-standard coding= practices continued and expanded in later releases, right up until the pre= sent? =0A=0ARon ---604106506-1248391825-1401822421=:27942 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hello

What is the issue with the Bitcoin code for 0.9.x with regard to asse= rtions that isn't in 0.8.6 or previous releases?

on April 18th, I offered
this commit and code with all side effects removed from the asserti= ons.

Then on the 28th,
this code with unit tests working.

And if that isn't enough, I did a video series on building Bitco= ind.exe and the static libraries (on MSVC++) all in NDEBUG (release) mode.<= /div>

=
See
https://www.youtube.com/playlist?list=3DPLFnWb= 0ttBBMLyUuniLp3PJ5Mn4tVUlliZ 
Notice that the NDEBUG release m= ode is featured, and I even run it!

Lastly what does that say about building Bitcoin-qt in rele= ase mode?  Should one or not??

There is also a video on buildin= g an alternate coin-qt.exe in release mode (gcc version) and running it!&nb= sp; See
https= ://www.youtube.com/watch?v=3DC8GvHpjbAnM

 


assert() should have no side effects, t= hat is the problem.

See
http://books.google.com/books?id=3D= L5ZbzVnpkXAC&pg=3DPA72&lpg=3DPA72&dq=3DGotcha+%2328+Side+Effect= s&source=3Dbl&ots=3DRn15TlPmje&sig=3DtymHqta0aSANwaM2GaXC-1Di_t= k&hl=3Den&sa=3DX&ei=3DuVKNU47fCcvTsAT6goHIBA&ved=3D0CCAQ6AE= wAA#v=3Donepage&q=3DGotcha%20%2328%20Side%20Effects&f=3Dfalse
a=0A great book, BTW.  Everyone who thinks they know what they are do= ing =0Awhen they write C++ should read this book!  They will realize t= hat they =0Adon't know Jack 3D"Roll

Why = weren't these and all the other examples of amateur, i.e., non-professional= , software fixed way back in version 0.3.0 in 2010, before any more release= s were done?  And why were these and other sub-standard coding practic= es continued and expanded in later releases, right up until the present?

Ron


=  
---604106506-1248391825-1401822421=:27942--