Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #3144
| From | Carlos <carlos@cvkm.cz> |
|---|---|
| Newsgroups | comp.lang.postscript |
| Subject | Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) |
| Date | 2017-07-26 16:41 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <20170726164132.25b1eb9a@samara.DOMA> (permalink) |
| References | (7 earlier) <20170704172151.27a32f78@samara.DOMA> <c5007832-5be8-4e86-b2ec-142251fc70e0@googlegroups.com> <9c61ec9b-2d69-4216-a18b-36c661c81dd4@googlegroups.com> <daa9484d-0b2d-4c25-ab85-2e9ec6ad22ee@googlegroups.com> <34e28872-ee7e-430e-a016-00146b8e7739@googlegroups.com> |
[luser droog <luser.droog@gmail.com>, 2017-07-25 23:07]
[...]
> Of course anyone with opinions, feel free to jump in.
I have, for now, having superficially perused the post, one superficial
opinion: I hate the redefinition of ">>". I'd reuse {}, making executable names
parameter names and literal names type names. That'd also allow having typed
and untyped parameters in the same function. Of course it'd also make
parameter parsing more complex.
Some examples to get a feel...
/arrayput { arr/arraytype idx/integertype item } { ... } func def
/fortuple { arr size/integertype proc/arraytype } { ... } func-begin def
[...]
> It may be desirable to add some addition "pattern" pseudo-typenames
> so you can check some of the arguments and use /any or /anytype to
> ignore the types of other arguments.
Or that's another possibility for untyped parameters, of course. I have some
unfinished multimethods (not exactly what you're doing but related) POC I'll
share in the evening, maybe there can be some cross-pollination of ideas :).
--
Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Control Structures luser droog <luser.droog@gmail.com> - 2017-06-21 22:50 -0700
Re: Control Structures Carlos <carlos@cvkm.cz> - 2017-06-23 00:28 +0200
Re: Control Structures luser droog <luser.droog@gmail.com> - 2017-06-23 00:01 -0700
Re: Control Structures luser droog <luser.droog@gmail.com> - 2017-06-28 10:57 -0700
Re: Control Structures luser droog <luser.droog@gmail.com> - 2017-06-28 21:25 -0700
Re: Control Structures luser droog <luser.droog@gmail.com> - 2017-06-30 03:05 -0700
Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-03 20:01 -0700
Binding - Re: Control Structures (Ordered Dictionaries) Carlos <carlos@cvkm.cz> - 2017-07-04 17:21 +0200
Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-09 10:44 -0700
Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-10 09:33 -0700
Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-15 20:00 -0700
Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-25 23:07 -0700
Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) Carlos <carlos@cvkm.cz> - 2017-07-26 16:41 +0200
Re: Type-checked function arguments - Re: Binding - Re: Control Structures (Ordered Dictionaries) luser droog <luser.droog@gmail.com> - 2017-07-26 10:29 -0700
csiph-web