Deutsch English Français Italiano |
<uv1q7n$3oohj$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro <ldo@nz.invalid> Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc Subject: Re: Command Languages Versus Programming Languages Date: Mon, 8 Apr 2024 22:14:16 -0000 (UTC) Organization: A noiseless patient Spider Lines: 72 Message-ID: <uv1q7n$3oohj$1@dont-email.me> References: <uu54la$3su5b$6@dont-email.me> <20240329101248.556@kylheku.com> <uu6t9h$dq4d$1@dont-email.me> <20240329104716.777@kylheku.com> <uu8p02$uebm$1@dont-email.me> <20240330112105.553@kylheku.com> <uudrfg$2cskm$1@dont-email.me> <87r0fp8lab.fsf@tudado.org> <uuehdj$2hshe$1@dont-email.me> <87wmpg7gpg.fsf@tudado.org> <LISP-20240402085115@ram.dialup.fu-berlin.de> <LISP-20240402091729@ram.dialup.fu-berlin.de> <wrap-20240402092558@ram.dialup.fu-berlin.de> <uui7hf$3gona$1@dont-email.me> <uuj1o5$3pvnq$1@dont-email.me> <87plv6jv1i.fsf@nosuchdomain.example.com> <wwv5xwyifq8.fsf@LkoBDZeT.terraraq.uk> <if-20240404121825@ram.dialup.fu-berlin.de> <uund4g$ugsb$1@dont-email.me> <uuofjh$19pfd$1@dont-email.me> <uuq0fp$1lcgf$2@dont-email.me> <86frvzo01i.fsf@williamsburg.bawden.org> <uuq4q9$1mbbf$1@dont-email.me> <20240408082037.00002d7c@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 08 Apr 2024 22:14:16 +0200 (CEST) Injection-Info: dont-email.me; posting-host="9e921ccf172b547a1f1ee9ff62d88dd1"; logging-data="3957299"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX182zJKf5a8ZUwSOdV5HFPvI" User-Agent: Pan/0.155 (Kherson; fc5a80b8) Cancel-Lock: sha1:y62Qf54Bbx68zxGdnNuIRlFy/dQ= Bytes: 4754 On Mon, 8 Apr 2024 08:20:37 -0700, John Ames wrote: > ... compulsively indenting and > splitting across lines can get out of hand, too. It seems to me that a > lot of people in this age of "cinematic" aspect ratios and super-sized > displays in personal computing forget that eye-travel isn't free, and > spreading information across maximal space can make it *harder* to keep > track of context. There it is again: “maximal space”. The “space” is there to be used. Code may be one-dimensional, but you have a two-dimensional screen to display it, why not make use of that, if it makes a complex structure clearer? Another example: def fill_in_depreciations(tax_year) : "(re)inserts depreciation entries for the specified tax year," \ " based on currently-entered assets." sql.cursor.execute \ ( "delete from payments where kind = %s and tax_year = %s", ["D", tax_year] ) for \ entry \ in \ get_each_record \ ( table_name = "assets, asset_depreciations", fields = [ "assets.description as description", "assets.initial_value as initial_value", "assets.when_purchased as when_purchased", "assets.depreciation_rate as rate", "assets.depreciation_method as method", "asset_depreciations.depreciation_amount as amount", ], condition = "assets.asset_id = asset_depreciations.asset_id and" " asset_depreciations.tax_year = %s", values = [tax_year] ) \ : sql.cursor.execute \ ( "insert into payments set when_made = %(when_made)s," " description = %(description)s, other_party_name = \"\"," " amount = %(amount)d, kind = \"D\", tax_year = %(tax_year)d" % { "when_made" : end_for_tax_year(tax_year) - 1, "description" : sql_string ( "%s: %s $%s at %d%% from %s" % ( entry["description"], entry["method"], format_amount(entry["initial_value"]), entry["rate"], format_date(entry["when_purchased"]), ) ), "amount" : - entry["amount"], "tax_year" : tax_year, } ) #end for #end fill_in_depreciations