From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a02:3b6e:: with SMTP id i46mr13545180jaf.16.1543870137642; Mon, 03 Dec 2018 12:48:57 -0800 (PST) X-Received: by 2002:aca:5395:: with SMTP id h143mr294020oib.6.1543870137362; Mon, 03 Dec 2018 12:48:57 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!news.muarf.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!k10no647004itk.0!news-out.google.com!v141ni771ita.0!nntp.google.com!q69no648267itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 3 Dec 2018 12:48:57 -0800 (PST) In-Reply-To: <31d76c8f-5e0b-4f64-88fd-34dcd63c19d6@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=208.114.128.47; posting-account=MRPdDAoAAADUJmZVjnYaoafXFMadSeY1 NNTP-Posting-Host: 208.114.128.47 References: <9524b3ee-476f-4af6-ab83-b15a6c2a417c@googlegroups.com> <6508fa19-5b93-471a-8b06-216907736b1b@googlegroups.com> <960eb922-6ea5-47d6-af48-289fff1f6fb5@googlegroups.com> <31d76c8f-5e0b-4f64-88fd-34dcd63c19d6@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: GNATCOLL JSON Parsing From: Olivier Henley Injection-Date: Mon, 03 Dec 2018 20:48:57 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:54934 Date: 2018-12-03T12:48:57-08:00 List-Id: >> I was talking about repositories with some doc. >> "amoc" -> no comment, except for copyright header Ok, we are not on the same page here.=20 The Amoc readme is super clear, no need for orthodox doc!=20 - Amoc has a screenshot, what you see is what you get. - Amoc has build procedure using gprbuild. The exact command line to build! - Amoc states the prerequisites, win32 and a Gnat compiler. - Amoc states a usage. "Launch the exe from the build". Cannot be clearer. - Amoc acknowlegde others work as a lead for further study. So you refer the ARM for people struggling with strings, but my repo is ope= n to 'interpretation'... you really want to cover this ground. Please. >> "aglw-demos" -> no comment either. You know that the github readmes as being doc is a thing these days..? Now = you know. Everything is there in the readme of Aglw-demos... for a WIP. The= src is 3 files, and the demo goal is exactly to offer a 'complete real cas= e usage' of the aglw lib API. I never said I should completely hold the hand of a newbie. You refer to ob= vious things, underline the tricky parts, you handout some meaningful use c= ase, in real code, and a normal person should be fine. I do not believe in 90's doc, a la MySQL, where you have to read dozens and= dozens of official doc to make a simple query or just to install it. No, w= hat is proper doc these days, is hands-on toy demo. You build it, inspect a= couple of files, you get the picture, c&p the basic code and expand from t= hat. You can keep rolling. Eg, gprbuild is awesome, but the doc is somewhat too much. I learn more fro= m inspecting others use of it that from the official doc. Do you see where I go? That was the point of the OP, I think, he just neede= d an 'almost' complete real use case, showed off. He would have picked from= there not problem.=20 You want a good example, check Imgui (https://github.com/ocornut/imgui) >> I did check before I commented... To me, not acknowledging the role of the readmes as the 'official doc' or p= roper 'comments' is bad faith from your part. >> In that single sentence, there are more comment than in all the reposito= ry. >> You actually fell to the same criticism you made earlier. Again, use the readmes. You know that, I know your repos. Some are dead cle= ar others are just empty. Look in your yard before picking on me. >> There is always someone for whom this isn't the case. That person needs = to >> report on that (and this thread was initially a good example of that:= a=20 >> problem with GNATCOLL.JSON," Talking of which. I started a project using GNATCOLL.JSON to unmarshal serv= er infos comming from Binance, one of, if not the main crypto exchange.=20 To my surprise I kept getting, errors, crash or empty data (I do not recall= exactly), with no leads what so ever. After some endless search on where t= he culprit was I decided to dig in GNATCOLL.JSON code. You bet, GNATCOLL.JS= ON did not handle word starting with a capital letter... yeah! And you bet = it did not report what is going wrong.=20 As you say we cannot pinpoint where ones knowledge starts/ends!=20 >> For the particular example I sent that resource is called the Ada Refere= nce >> Manual. A bit of disconnection here. Learning ways of bread and butter Ada code (st= rings manip) from the ARM is like studying quantum mechanics to understand = why you should refrigerate milk. I'm joking ... almost not. >> Every little progress will be nice. Don't think though that Ada will bec= ome >> mainstream again, that time has passed, and a lot of people just pre= fer to >> look at the new and shiny. C++ has never been so hyped! They work for the hype, they believe in it, th= ey play the 'real man' game (vs the script kiddies culture) without being m= undane and it works.=20 >> I know this is ironic, but you would not believe the number of request f= or >> help that have exactly that tone. Tell them to go to hell. >> That won't work. What works is publishing things (Code, tutorials, doc,.= ..)=20 I know publishing things is the key, but a reality check is always good. Th= e OP is right. =20 >> Your list of awesome-ada seems like it could be a good starting point. B= ut >> if you don't advertise it, this is wasted effort.=20 I did not advertise it because it misses obvious things, see the TODO at th= e end. =20 >> And as soon as you advertise it, you will get comments from people "your= =20 >> list is stupid because it doesn't include such and such"... Then you wil= l >> become part of the middle-aged guard. I have no problem handling such people, and it is no argument to not proper= ly engage in 'demonstrating' how our projects/libs etc works in a modern wa= y.