Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #94616

Re: Gmail eats Python

Show all headers | View raw

Chris Angelico <rosuav@gmail.com>:

> On Sun, Jul 26, 2015 at 7:51 PM, Marko Rauhamaa <marko@pacujo.net> wrote:
>>> - What everyone calls head (of a list) emacs calls Car (Toyota?)
>>
>> Now you're inventing things.
>
> No, but it's LISP rather than Emacs that calls it that.

You'd have to get into programming lisp before you encountered "car" in
emacs. It's much easier to grasp than "class" in Python.

Python still retains "lambda", BTW. And what are "strings", "floats",
"braces" and "sockets"? Only "bubblegum" and "ducktape" are missing
(however, "ducktype" is included).

> And it dates back to an assembly language opcode. Why that got
> perpetuated in a high level language, I don't know - it'd be like
> building a language today and using "interrupt" as the name of its
> call mechanism, because it's built on the Intel INT opcode.

It is funny, that's for sure. It comes from the time when the mechanics
of a computer inspired much more awe with the theorists than it does
nowadays.

The separation between layers of abstraction is a never-ending challenge
in our profession.

An anecdote:

Back in the late 80's I had to deal with the GSM MAP protocol. In
protocol layers, you would find MAP on top of the protocol stack as
follows (go go gadget M-x picture-mode):

        +-------+
        | MAP   | application
        +-------+
        | ASN.1 | presentation
        +-------+
        | TCAP  | transaction
        +-------+
        | SCCP  | session
        +-------+
        | MTP3  | network
        +-------+
        | MTP2  | link
        +-------+
        | T1/E1 | wire
        +-------+

Now you express MAP data abstractly using ASN.1's abstract notation.
Phone numbers are defined (somewhat less abstractly) as hexstrings. If
the phone number is

   1234567

you express that in MAP as

   '214365F7'H

Huh?

I wondered that aloud to Nokia Network's GSM specialist. He thought
about it for a while and then said, "Well, that way the phone number
bits go out on the wire in the right order."

In telephony protocols, the least significant bit is transmitted first
on the serial wire. So, if you want the first digit (1) to go out first,
you have to place it in the lower nibble of the first octet (in the BER
encoding of ASN.1).

I was left speechless.


Marko

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-25 20:47 +0300
  Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-25 20:52 +0300
    Re: Gmail eats Python Laura Creighton <lac@openend.se> - 2015-07-25 20:05 +0200
      Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:26 +0300
  Re: Gmail eats Python Jon Ribbens <jon+usenet@unequivocal.co.uk> - 2015-07-25 18:44 +0000
  Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-25 22:42 +0300
    Re: Gmail eats Python Ben Finney <ben+python@benfinney.id.au> - 2015-07-26 10:52 +1000
    Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 10:58 +1000
    Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:01 +0300
      Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-25 22:28 -0700
        Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 15:34 +1000
          Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-25 23:15 -0700
            Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 16:25 +1000
              Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 09:55 +0300
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 01:20 -0700
                Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 11:35 +0300
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 01:50 -0700
                Re: Gmail eats Python alister <alister.nospam.ware@ntlworld.com> - 2015-07-26 09:21 +0000
                Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 12:27 +0100
                Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 12:51 +0300
                Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 20:03 +1000
                Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 13:31 +0300
                Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 14:30 +0300
                Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 14:48 +0300
                Re: Gmail eats Python random832@fastmail.us - 2015-07-29 10:51 -0400
                Re: Gmail eats Python Larry Martell <larry.martell@gmail.com> - 2015-07-29 10:53 -0400
                Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 13:43 +0300
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 06:16 -0700
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-28 20:35 -0700
                Re: Gmail eats Python Laura Creighton <lac@openend.se> - 2015-07-29 18:32 +0200
              Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 15:42 +0000
            Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 12:25 +0100
        Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 15:47 +0000
          Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 08:59 -0700
            Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 18:21 +0100
            Re: Gmail eats Python Steven D'Aprano <steve@pearwood.info> - 2015-07-27 03:40 +1000
              Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 14:34 -0700
              Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-27 11:47 +1000
            Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 19:45 +0000
              Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 14:54 -0700
  Re: Gmail eats Python Steven D'Aprano <steve@pearwood.info> - 2015-07-26 14:49 +1000
    Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:37 +0300

csiph-web