log☇︎
30 entries in 0.382s
mircea_popescu: spyked, guids in rss are the postid, this isn't exactly arbitrary, it's a numeric gensym for the article -- guaranteed to monotonically increase over time.
mp_en_viaje: well anyway, regardless of implementation, the design idea there is that article title always has a ready gensym in the shape of the numeric id of the table entry, which is unique and always known and therefore should be the fallback default.
a111: 26 results for "gensym", http://btcbase.org/log-search?q=gensym
asciilifeform: !#s gensym
asciilifeform: http://btcbase.org/log/2018-06-09#1821831 << i gotta wonder, when meeting people in meatspace, does he also make up gensym names each time he shakes a hand.. ☝︎
mircea_popescu: http://btcbase.org/log/2018-05-21#1816338 << possibly do a composite, "time program was called"+gensym. that'll resolve the conflict. ☝︎
a111: Logged on 2018-03-28 19:32 asciilifeform: funnily enuff, if working rng were standard on pc, 128bits from it would give unique-gensym ( the supposed problem , according to the gcc nitwits, with mktemp , is collision ) without O(N) searching ( as in mkstemp) with probability ~1
asciilifeform: ( if you need a heavy-duty gensym, http://btcbase.org/log/2018-03-28#1790082 works and is easy to implement ) ☝︎
phf: asciilifeform: that's not going to work cross-invocations though. gensym is incremental across the instance, so same invocations should produce roughly same gensym numbers
asciilifeform: esthlos: (gensym)
ben_vulpes: esthlos: i made a gensym dir in /tmp, passed that to gpg for the workdir, and then various operations take a teardown key, defaulting to true which could be overriden to inspect keyring state should the operator so desire
asciilifeform: funnily enuff, if working rng were standard on pc, 128bits from it would give unique-gensym ( the supposed problem , according to the gcc nitwits, with mktemp , is collision ) without O(N) searching ( as in mkstemp) with probability ~1 ☟︎
mircea_popescu: tring is secret gensym ; gensym is public trng.
a111: 15 results for "gensym", http://btcbase.org/log-search?q=gensym
asciilifeform: !#s gensym
mircea_popescu: http://btcbase.org/log/2018-01-05#1765100 << this is a gensym in the sense girl you met at butcher's is your true love. why not call gns like sane people. ☝︎
asciilifeform: ( have a gensym. there is no excuse ever to be hosed by a previous unsuccessful run. )
asciilifeform: but description is general , re 'how to make non-predictable gensym'
mircea_popescu: (also why i said no above to "gensym")
asciilifeform: a gensym, in case anyone forgot, is defined as a symbol that is guaranteed to be unequal to all other invocations of gensym.
asciilifeform: mircea_popescu's solution, if i understand it, is to include a gensym in each patch body.
asciilifeform: phf: then keep a (gensym) thing on the server you can call.
asciilifeform: in lisp parlance, it has to be a 'gensym'
ascii_field: (this-bloke (gensym) (walked-into (bar)))
asciilifeform: (of course, a gensym, if not garbage collected, also occupies a cell of memory)
asciilifeform: (gensym) just coughs up a guaranteed-unique object.
gribble: GENSYMs - Common Lisp HyperSpec (TM): <http://clhs.lisp.se/Body/f_gensym.htm>; Macros: Defining Your Own - gigamonkeys: <http://www.gigamonkeys.com/book/macros-defining-your-own.html>; hygiene-versus-gensym - Community-Scheme-Wiki: <http://community.schemewiki.org/?hygiene-versus-gensym>
asciilifeform: ;;google gensym common lisp
gribble: Gensym | Real-Time Management of Mission Critical Systems: <http://www.gensym.com/>; Product | Gensym: <http://www.gensym.com/en/product>; Gensym G2 2011 EDITIONS – Product Detail | Gensym: <http://www.gensym.com/en/product/G2>
asciilifeform: ;;google gensym