Date: Tue, 14 Jul 2020 11:27:52 -0400 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Petite Cloud, CBSD, Intellij Message-ID: <CAGBxaX=qoTRkUZ8Rc7AU3nv4%2Bb0%2BZQ0D1zr4OwMTAj7MSLnDUQ@mail.gmail.com> In-Reply-To: <20200714151237.GA28670@mithril> References: <CAGBxaX=QvJqSycQJrq3RmFJ57E=ebSY6sG2BTXpUKBP5jpqw6g@mail.gmail.com> <8fcd60d7-1de1-82dc-d840-2555663ac153@gmail.com> <CAGBxaXn9tq6hbbNdjn_iqSiSr74exO1G-M9=eyP6YHykQ8QctA@mail.gmail.com> <bae2f4df-ec82-5beb-57ae-a07a5460a48a@gmail.com> <CAGBxaX=AuFx2fd0vwK0MTvSjvrrMZhNsG1TqecbFrAkqge96CA@mail.gmail.com> <20200714070831.f01a144e1dc808ebea421afe@sohara.org> <CAGBxaXmQ8zfqU%2B5kT1RAcQph4wfQ8mT8LKQC%2BS_J8eePyEpgQg@mail.gmail.com> <20200714104735.ceae71903e2f61bf401655ea@sohara.org> <8f96ee4e-2922-7850-6839-1c50a62094fe@gmail.com> <20200714153626.62ade8ec.freebsd@edvax.de> <20200714151237.GA28670@mithril>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 14, 2020 at 11:13 AM Jacques Foucry <jacques+freebsd@foucry.net> wrote: > > > Whew! I was afraid I'd managed to start a *real* flame war, one of > those > > > endless my-language/your-language pissing matches. :D > > > > Don't worry! Experienced programmers _know_ that you can write > > crappy code in _every_ language - it's just the fact the some > > languages encourage writing bad code more than others if the > > programmer did not properly learn the language's elements and > > its adjacent tools. :-) > > And others (like COBOL[1]) are strictly discourage bad/non reading code. > COBOL is the very definition of a language that encourages bad code (assembly is the only one that is worse). One of the worst offending items is a construct (I forget the actual code) that boils down to goto with a symbolic (and changeable at run time) goto. The only thing worse then this when keeping with the unconditional arbitrary instruction pointer changing theme (aka "goto considered harmful") is a hypothetical construct I have joked about I call "dynamic camefrom". Camefrom says to go back to the last location that executed a goto (think of it as an unstructured return/break/continue that can be used between functions and outside of loops). The dynamic camefrom lets you at runtime symbolically specify how many gotos to jump over when going back to where you came from (it is a seg fault/core dump if you specify a number of gotos that is greater then the number executed so far in the program or if it is negative). The icing on the cake would be a purely dynamically typed language that implies type by first assignment (such as JavaShit) implementing dynamic camefroms. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGBxaX=qoTRkUZ8Rc7AU3nv4%2Bb0%2BZQ0D1zr4OwMTAj7MSLnDUQ>