9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] void*
Date: Mon, 16 May 2022 06:23:31 -0700	[thread overview]
Message-ID: <AD04414B-D360-41CF-81E6-8B2D54A9216C@iitbombay.org> (raw)
In-Reply-To: <CAJSxfmJ7c_9-+f_rjC-CXvaTzBNi+0puzT8Jx8rqEHGO-51LmQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]

I can see some use of void* arithmetic for malloc/free or
when you’re doing your own allocation for various object
types, where a size of 1 would be handy.

I wonder what a FarC would like!

> On May 15, 2022, at 11:27 PM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> 
> 
> If void can have a size, why not 4, 8 or 16?
> 
> P.S. I discovered Gholami Rudi's work a little while ago. I was especially intrigued by Farsi support in neatroff (intro in Farsi produced by Neatroff and Neatpost: https://litcave.rudi.ir/neatfarsi.pdf <https://litcave.rudi.ir/neatfarsi.pdf>)  Cool stuff.
> 
> 
> On Sun, May 15, 2022, 9:09 AM adr <adr@sdf.org <mailto:adr@sdf.org>> wrote:
> In case someone is asking why this guy is suddenly so thoughtful
> about void pointers, it is because I'm porting Ali Gholami Rudi's
> neatroof, and he uses a lot of arithmetics with void* in neatmkfn.
> I got rid of ape, and this troff looks really easy to port and has
> a lot of features. I'll share it when it's working in case someone
> is interested.
> 
> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/Tecaea3b9ec8e7066-M683ed8fb049de7a5d4457cbf <https://9fans.topicbox.com/groups/9fans/Tecaea3b9ec8e7066-M683ed8fb049de7a5d4457cbf>
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription <https://9fans.topicbox.com/groups/9fans/subscription>
> 9fans <https://9fans.topicbox.com/latest> / 9fans / see discussions <https://9fans.topicbox.com/groups/9fans> + participants <https://9fans.topicbox.com/groups/9fans/members> + delivery options <https://9fans.topicbox.com/groups/9fans/subscription>Permalink <https://9fans.topicbox.com/groups/9fans/Tecaea3b9ec8e7066-M9e20019333d1d1dbde3a2c3d>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tecaea3b9ec8e7066-M5831ffd0a329bdcb8294ee6b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3764 bytes --]

  parent reply	other threads:[~2022-05-16 13:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 10:58 adr
2022-05-15 12:11 ` Humm
2022-05-15 13:03   ` adr
2022-05-15 13:15     ` adr
2022-05-15 13:21       ` arnold
2022-05-15 14:09         ` adr
2022-05-15 14:47           ` ori
2022-05-15 15:49             ` adr
2022-05-15 15:23       ` Dan Cross
2022-05-15 15:50         ` Bakul Shah
2022-05-15 15:54           ` ori
2022-05-15 14:46 ` ori
2022-05-15 16:07 ` adr
2022-05-16  6:24   ` Skip Tavakkolian
2022-05-16 12:46     ` Humm
2022-05-16 13:23     ` Bakul Shah [this message]
2022-05-16 14:46 ` Charles Forsyth
2022-05-16 16:03   ` adr
2022-05-16 17:45     ` hiro
2022-05-17  4:00       ` Lucio De Re

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=AD04414B-D360-41CF-81E6-8B2D54A9216C@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=9fans@9fans.net \
    /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).