Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-10-05

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:01 ronsavage JK; block_where() strikes me as a very awkward name. How about block_stats() or block_indexes() or block_track() or block_offsets()?
00:02 ronsavage And what values does <end of read> return? I assume 0 & 1.
00:35 ronsavage Or even block_tracker().
01:55 ilbot3 joined #marpa
01:55 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Code paste/run: https://f.perlbot.pl/#marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today - Youtube channel: https://www.youtube.com/channel/UCYKVfGBtfTqbs1JdYq-dc5g
02:34 ronsavage joined #marpa
02:36 idiosyncrat joined #marpa
02:38 idiosyncrat re https://irclog.perlgeek.de/marpa/2017-10-05#i_15258262
02:38 idiosyncrat Thanks for the feedback.
02:38 idiosyncrat block_stats() -- too vague.
02:40 idiosyncrat block_indexes() -- in my (new) terminology a block "location" or "position" is composed of an <id, offset> pair.  In this context it's not clear what "index" means.
02:40 idiosyncrat block_offsets() -- "offset" is one of the elements it returns, so one is not quite right.
02:41 idiosyncrat block_track() -- that may be a good idea.  It thought block_where() was clear in suggesting it tells you "where" you are in the block.  Does "track" strike you as clearer?
02:42 idiosyncrat re "end of read"
02:43 ronsavage block_track() is ok, but I've just thought of block_status(), since it returns a status report of block/offset items.
02:43 idiosyncrat In R2, you had only one input string, but could move around within it, and confine reading to portions of it, with the end point being called IIRC "end of input".  This was by default the physical end of the input string, but using $recce->read() and $recce->resume() you could set it earlier.
02:44 idiosyncrat "end of read" is the same thing for blocks.  You can instruct Marpa to confine reading within a block to a certain range, and the end of that range is "eoread" or "end of read".
02:45 ronsavage As for 'end of read', I took that to be a flag indicating whether or not the last read reached end of physical input. What do you see it as indicating?
02:46 ronsavage Hmm. OK. Not clear. Why /set/ that in a call which /returns/ info? Or an I misunderstanding?
02:47 idiosyncrat I don't like block_status() because it's vague, whereas block_where() specifically returns information about your position within the block -- location information -- block_where() suggests that, and so does block_track().  "track" to my ear conveys the idea of "tracking" someone's location.
02:47 ronsavage Exactly. I see this call tracking progress!
02:48 idiosyncrat "State" to my ear means things like "in use", "initialized", etc etc, which isn't what block_where() tells you.
02:48 ronsavage As for end of read, so are you saying it returns info re the users previously set option of reading within blocks as opposed to across blocks?
02:48 idiosyncrat Yes.
02:49 idiosyncrat It tells you your current position in the block and how much further you'll be allowed to read.
02:49 ronsavage I chose state because to me it's answering the question: What's the state of reading at this point in time? block_state() sounds OK to me.
02:49 idiosyncrat Also, if you don't provide a $block_id argument, it tells you which block is your current block.
02:49 ronsavage OK. Then how about block_progress() as in progress report?
02:51 idiosyncrat Or in the phrase "track progress"?  Of the two words, I like "track" more, if only because it's shorter.
02:52 idiosyncrat block_track() does have the advantage that the other block_*() methods often end in verbs: block_set(), block_move().  Even the "new" in block_new() is effectively a verb the way it's used in OO.
02:53 ronsavage Perhaps  now you can see why I suggested block_status/state(), since progress report is very much like status report :-).
02:54 ronsavage I still like block_tracker() since it suggests you're getting back a block track/progress report.
02:56 idiosyncrat I try to be consistent.  "Tracker" is a noun, "track" is a very, and the other block calls (except the constructor) are verbs.
02:56 idiosyncrat s/very/verb/
02:57 ronsavage Yep - I have no problem with you choosing a verb. Exit 'block_where()'. Hahaha.
03:00 ronsavage But choosing an inappropriate name just because it's a verb has to be a nono. So I vote for block_progress(). And anyway: Perhaps leave it for a few hours for your mind to mull over these details. And the # of choices suggests we're in the right area now, and these names all convey the idea, but only one can be chosen.
05:27 idiosyncrat I've deleted the pause_span() method.  It could not handle multiple input blocks and was already deprecated in favor of using the arguments passed to the event handlers.
06:41 ronsavage joined #marpa
09:21 koom joined #marpa
09:58 koom_ joined #marpa
17:22 koom_ joined #marpa
21:57 ronsavage joined #marpa

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary