From: Ryan Gonzalez <rymg19@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
Bakul Shah <bakul@bitblocks.com>
Subject: Re: [9fans] ot: pascal rides again?
Date: Sun, 24 May 2015 14:36:42 -0500 [thread overview]
Message-ID: <A3EDFFE5-EFA1-4D1A-AD60-AAF54363BEB2@gmail.com> (raw)
In-Reply-To: <869357D2-F7D2-457C-AC03-0E29870328A6@bitblocks.com>
On May 24, 2015 2:00:05 PM CDT, Bakul Shah <bakul@bitblocks.com> wrote:
>
>
>On May 24, 2015, at 8:55 AM, erik quanstrom <quanstro@quanstro.net>
>wrote:
>
>>> Uhm I might be mistaken, but I guess [8192]byte is an array, and
>[]byte are
>>> slices - therefore they are different types.
>>
>> yes, exactly. i suppose this implies that different size arrays are
>not type compatable
>> (yea pascal). also the fu := bar[:] looks a lot like the tedious
>casting from c, and implies
>> dynamic allocation of the slice, i'm guessing.
>>
>> - erik
>>
>Later pascal standards supported conformant array parameters. And
>several extended pascal compilers provided dynamic arrays.
>
>In Go multidimensional arrays are not well supported. Try this:
>
>var x [5][6]int
>y := x[:2][:3]
>fmt.Printf("%v\n", y)
>
>It is what it is. Get used to it if you want/have to use Go! Apart from
>its concurrency features it is a pretty boring language but it is
>surprisingly easy to write code in it.
Seriously. I like Nim better. And K...
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2015-05-24 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 15:53 erik quanstrom
2015-05-23 16:17 ` Eduardo Alvarez
2015-05-23 16:26 ` Aram Hăvărneanu
2015-05-23 18:14 ` C Cirello
2015-05-23 18:25 ` Ryan Gonzalez
2015-05-24 15:55 ` erik quanstrom
2015-05-24 16:19 ` Devon H. O'Dell
2015-05-24 17:02 ` Aram Hăvărneanu
2015-05-24 17:53 ` Ryan Gonzalez
2015-05-24 17:50 ` Ryan Gonzalez
2015-05-24 19:00 ` Bakul Shah
2015-05-24 19:36 ` Ryan Gonzalez [this message]
2015-05-24 21:25 ` minux
2015-05-25 1:26 ` C Cirello
2015-05-25 5:39 ` lucio
2015-05-25 7:59 ` Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A3EDFFE5-EFA1-4D1A-AD60-AAF54363BEB2@gmail.com \
--to=rymg19@gmail.com \
--cc=9fans@9fans.net \
--cc=bakul@bitblocks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).