poke-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [POLL] Syntax to refer to IO spaces by name


From: Dan Čermák
Subject: Re: [POLL] Syntax to refer to IO spaces by name
Date: Fri, 22 May 2020 21:08:37 +0200

"Jose E. Marchesi" <address@hidden> writes:

> Hi people!
>
> Up to now we have been referring to IO spaces using tags of the form #N
> where N is the IOS id.  Example:
>
> (poke) .info ios
>   Id  Mode    Size            Name
> * #1          0x00001000#B    *scratch*
>   #0  rw      0x000004c8#B    ./foo.o
> (poke) .ios #0
> The current IOS is now `./foo.o'.
>
> It is time to add the ability to refer to IO spaces by name instead.
> So, what would you prefer:
>
> a) #[NAME], examples: #[*scratch*], #[./foo.o]
> b) #"NAME", examples: #"*scratch*", #"./foo.o"
> c) #<NAME>, examples: #<*scratch*>, #<./foo.o>
>
> Opinions?  My favorite is b), at the moment.

I'd go with b) as well.

>
> PS: note that at some point we will probably separate the notions of
>    "name" and "handler" for IO spaces, i.e. the name of the IO space
>    will be derived from the handler, like in:
>
>    .file ./foo.o
>    .file /usr/bin/foo.o
>
>    Will open two IO spaces with names "foo.o" and "bin/foo.o", for
>    example.  This will make it easier to refer to the spaces than using
>    the full /usr/bin/foo.o or ../bleh/foo.o.

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]