The prefixes are based on this file:
https://github.com/racket/gui/blob/master/tex-table/tex-table.rkt
Maybe there are missing ones you're used to?
Sorry, that was supposed to be a compliment! I love DrRacket's support
for unicode and I havent wanted any symbols that aren't already
supported.
I am using a cmd-name! naming format for functions that are adding to the
command list that will be communicated to the host program.
(cmd-sound! WAV-FILE)
(cmd-set-position! pos yaw-radians)
Etc.
I am considering using a terser naming convention, perhaps @name, so you
would have:
(@sound
You also have unicode available to you. IDE support can help with this
-- I think the cmd-\ for lambda has worked pretty well.
I've been going this route more, especially because DrRacket supports
autocompletion of (what it deems) unique latex prefixes. For example,
in DrRacket, type \G,
I tried $ first, but it scans so close to an S that it hurt readability.
-Original Message-
From: Greg Hendershott [mailto:greghendersh...@gmail.com]
Sent: Friday, July 03, 2015 11:53 AM
To: John Carmack
Cc: racket-users@googlegroups.com
Subject: Re: [racket-users] API function naming
What symbols have the least historic baggage?
I've gone through this exercise a few times, and each time settled on '$'.
As Greg points out, pretty much every one of my my Racket libraries
makes use of this symbol (was it that obvious? :) ) exactly because I
was looking for something that
I'd avoid @ because it's used for at-expressions, e.g. #lang
scribble or even simply #lang at-exp racket.
On Fri, Jul 3, 2015 at 12:32 PM, John Carmack jo...@oculus.com wrote:
I am using a “cmd-name!” naming format for functions that are adding to the
command list that will be communicated to
We clearly need keyboards like this:
http://9gag.com/gag/5551148/the-entire-chinese-keyboard
On Fri, Jul 3, 2015 at 1:43 PM, Stephen Chang stch...@ccs.neu.edu wrote:
The prefixes are based on this file:
https://github.com/racket/gui/blob/master/tex-table/tex-table.rkt
Maybe there are missing
One idea is to use $ as prefix.
It probably connotes command among Unix-y folks, at least.
(Although I've seen $ used as a prefix in e.g. combinator libraries
like Parsack, I don't think it has any universal meaning like that
which would make it seem weird for your purposes?)
On Fri, Jul 3,
You also have unicode available to you. IDE support can help with this
-- I think the cmd-\ for lambda has worked pretty well.
Robby
On Fri, Jul 3, 2015 at 12:36 PM, Stephen Chang stch...@ccs.neu.edu wrote:
What symbols have the least historic baggage?
I've gone through this exercise a few
1. +1 on Neil's +sound and +set-position convention (as a private Racket
citizen not the style guide author)
2. When I find myself writing such code now, I often write a syntactic
extension that gives me some flexibility in how I want to do it:
(commands
(sound ...)
(set-position ...)
General comment on the naming conventions we come up with... These
punctuation characters that typically require a shift modifier might be
pleasing to the eye, but unpleasing to the typist.
Incidentally, while @ might have lower typing cost than cmd-, I
think it's more than 1/4 the typing
On 07/03/2015 12:32 PM, John Carmack wrote:
I am using a “cmd-name!” naming format for functions that are adding to
the command list that will be communicated to the host program.
(cmd-sound! WAV-FILE)
(cmd-set-position! pos yaw-radians)
Etc.
I am considering using a terser naming
Alexis King wrote on 07/03/2015 06:33 PM:
Perhaps this isn’t applicable in this case, but may I suggest a less-common
alternative: no prefixing at all? If you put all the commands into a separate
module, users of the module can use ‘prefix-in’ to choose whatever prefix they
prefer.
For
Perhaps this isn’t applicable in this case, but may I suggest a less-common
alternative: no prefixing at all? If you put all the commands into a separate
module, users of the module can use ‘prefix-in’ to choose whatever prefix they
prefer.
This can be paired with documentation that uses a
Perhaps this isn’t applicable in this case, but may I suggest a less-common
alternative: no prefixing at all? If you put all the commands into a separate
module, users of the module can use ‘prefix-in’ to choose whatever prefix
they prefer.
Prefixes (and suffixes) have two purposes. One is
15 matches
Mail list logo
