00:00:00 --- log: started forth/20.01.10
00:50:02 --- join: xek__ joined #forth
00:55:06 --- quit: WickedShell (Remote host closed the connection)
01:27:28 --- join: dys joined #forth
01:44:00 --- join: dddddd joined #forth
02:21:42 --- join: mtsd joined #forth
02:30:35 --- quit: mtsd (Remote host closed the connection)
02:35:36 --- join: mtsd joined #forth
02:40:41 --- quit: proteusguy (Ping timeout: 268 seconds)
02:55:59 --- join: iyzsong joined #forth
03:07:29 --- join: proteusguy joined #forth
03:07:29 --- mode: ChanServ set +v proteusguy
04:55:11 --- quit: rdrop-exit (Quit: Lost terminal)
04:58:24 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in)
05:40:54 --- quit: mtsd (Quit: Leaving)
06:16:57 <crc> crab1: I haven't had a chance to work on HTTP POST yet, but here's an example using sockets to do an HTTP GET: http://forth.works/examples/http-get.retro.html
06:59:16 <crc> crab1: HTTP POST is only slightly more complex to implement: http://forth.works/examples/http-post.retro.html
07:17:36 --- quit: dave0 (Quit: dave's not here)
08:52:18 --- join: X-Scale` joined #forth
08:53:34 --- quit: X-Scale (Ping timeout: 268 seconds)
08:53:35 --- nick: X-Scale` -> X-Scale
09:11:54 --- quit: dys (Ping timeout: 248 seconds)
10:03:46 --- join: dys joined #forth
10:10:58 --- join: proteus-guy joined #forth
10:25:43 --- join: WickedShell joined #forth
10:26:33 --- quit: dys (Ping timeout: 258 seconds)
12:06:50 --- join: Labu joined #forth
12:07:06 --- part: Labu left #forth
12:07:07 --- join: Labu joined #forth
13:06:30 --- join: dave0 joined #forth
13:12:01 --- quit: gravicappa (Ping timeout: 265 seconds)
15:06:09 --- join: dys joined #forth
15:12:58 <tpbsd> g'day Forthiers
15:47:06 <crc> Hi tpbsd
15:47:30 <tpbsd> g'day crc
15:49:48 <crc> How are things down under?
15:50:35 <tpbsd> hot today at 36C but forcast down to 25C tomorrow with rain
15:50:52 <tpbsd> hopefully the rain will keep it's appointment
15:51:29 <tpbsd> how is Retro today under your curative care ?
15:52:47 <crc> All I did today was write http get and post words
15:54:05 <tpbsd> I know, I copped them into my crowing collection of Retro doc :)
15:54:20 <crc> :)
15:54:53 <tpbsd> I havent started trying to use retro yet as I still have some updates and a new Forth program to develop
15:55:14 <tpbsd> but first retro cab of the rank will be to look at your html converter
15:55:31 <tpbsd> as html plays a big part in my Forth docs
15:56:03 <tpbsd> it will be a good first use involving PC files and retro
16:07:03 --- join: ryke joined #forth
16:38:59 --- join: jsoft joined #forth
16:57:33 <crab1> good evening
17:01:30 <crab1> oh, did the http example go well?
17:20:31 <crc> crab1: yes
17:23:31 <crab1> good :)
17:34:40 --- join: iyzsong joined #forth
17:44:34 --- join: smokeink joined #forth
18:17:34 --- part: Phoenixwater[m] left #forth
18:21:13 --- quit: dddddd (Ping timeout: 240 seconds)
18:45:43 --- quit: dave0 (Quit: dave's not here)
19:18:40 <jsoft> tpbsd, I will have you know, slow cooked/crock pot lump of beef roast turned out EPIC
19:18:57 <jsoft> tpbsd, I just put some rub on it, salt, and shoved it in. No water, or anything
19:19:02 <jsoft> tpbsd, it was awesoem
19:19:08 <jsoft> And also awesome
19:19:21 <jsoft> Well it still is, I have no eaten all of it yet :)
19:19:47 <tpbsd> mercury always brings out the flavor in meat I find
19:20:19 <tpbsd> heavy metal ceramic, yum!
19:21:00 <jsoft> Nah I brought some chineese anti heavy metal filters
19:21:45 <jsoft> I think I might try a kg or two of mince next
19:22:10 <tpbsd> slow cooked mince ?
19:22:23 <jsoft> Yeah why not
19:22:41 <jsoft> With bacon and other bits
19:23:23 <tpbsd> while you were stuffing your face with radioactive slow cooked beef, I was writing Forth code :P
19:23:38 <jsoft> Well someones got to eat
19:23:49 <tpbsd> 34,43 C 
19:23:50 <tpbsd> 94,09 F
19:23:51 <jsoft> What ya been working on now?
19:24:02 <tpbsd> and someone has to advance the state of Forth on embedded
19:24:16 <jsoft> Sweet you do that, I'll eat
19:24:23 <jsoft> :D
19:24:29 <tpbsd> :P
19:24:53 <tpbsd> two things, a new refined memstat utility and the new XonXoff Word
19:25:08 <jsoft> What is the xon xoff thing again?
19:25:34 <tpbsd> hahah, beef certainly doesn't seem to help short term memory
19:26:03 <tpbsd> then I'll be integrating Retro Forth into my Forth documentation system
19:26:39 <jsoft> Nah its some shit about flow control, I know that from ages ago. But I cant remember if you actually explained it, or just said something about heavy metals
19:26:56 <jsoft> Retro forth even
19:27:09 <tpbsd> it's just software based flow control
19:27:24 <jsoft> How does it work tho
19:28:17 <jsoft> Google and other search engines are not available in my country whilst they wait till you answer the question :P
19:28:21 <tpbsd> XOFF is used by a receiving device as a way to let the transmitting device know it needs to stop transmitting. When the device is ready to recommence, the XON character is sent.
19:29:19 <jsoft>  So then it cannot be sending normal binary, as two bytes are used for XONXOFF ?
19:29:21 <tpbsd> it's obvious your google-fu is severely retarded
19:29:27 <jsoft> I never tried it.
19:29:36 <jsoft> I would rather you explain it :P
19:29:42 <tpbsd> terminals dont send binary, theyre ascii only
19:30:05 <jsoft> Ok so its not for normal uC to device comms, its terminal only
19:30:24 <jsoft> I guess for your uploading of code and shit, I am assuming
19:30:25 <tpbsd> there does seem to be a severe lack of basic comms understanding here today
19:30:43 <tpbsd> terminals are all ASCII
19:30:54 <tpbsd> ASCII != binary
19:31:01 <jsoft> Well I dunno, i've never thought about what a 'terminal' is.
19:31:06 <jsoft> Its just sending bytes to me.
19:31:12 <tpbsd> ascii = 7 bit data, binary = 8 bit data
19:31:26 <tpbsd> I guess most people dont think about it
19:31:43 <tpbsd> comms is just one of those day to day things that usually works
19:31:45 <jsoft> tpbsd, I do not think I have ever used anything with 7 bits
19:32:23 <tpbsd> in your Linux box type "man ascii"
19:32:35 <tpbsd> youll see what I mean
19:33:00 <jsoft> yeah so
19:33:12 <tpbsd> 7 bit ascii consists of 'printing characters' and 'control characters'
19:33:20 <jsoft> Its < 128, but who uses 7 bits nowdays?
19:33:35 <tpbsd> I suppose I should do a page about this on my doc site
19:33:47 <jsoft> What actually uses 7 bits
19:33:49 <jsoft> seriously
19:33:54 <tpbsd> Mecrisp-Stellaris ?
19:34:03 <jsoft> :|
19:34:33 <jsoft> if I sent it 0xFF it would explode?
19:34:33 <tpbsd> 8 bit ascii is called "unicode" I believe
19:34:48 <jsoft> I thought unicode was 2 bytes
19:34:49 <tpbsd> hahah, good one
19:35:03 <tpbsd> maybe it is, I dont know anything about unicode
19:35:08 <jsoft> Neither
19:35:15 <tpbsd> 0xFF is ascii
19:35:23 <tpbsd> as is 256
19:35:24 <jsoft> Oh its ascii now is it
19:35:29 <jsoft> 8 bits then
19:35:54 <tpbsd> ok, you type 0xFF in binary here then ?
19:36:07 <tpbsd> ... waiting
19:36:13 <jsoft> 11111111
19:36:28 <tpbsd> wrong, thats ascii
19:36:39 <jsoft> oh ok, you are being a dick
19:36:52 <tpbsd> id rather be a dick than a idiot
19:37:15 <jsoft> You know full well I was using 0xFF as the value of a byte.
19:37:16 <tpbsd> hint: if you can read it here, it's ASCII
19:37:36 <jsoft> ASCII is just a character set matched up to a value.
19:37:40 <tpbsd> i know you were using a ASCII representation of 256 in binary
19:37:50 <jsoft> 255 actually.
19:37:51 <tpbsd> ??
19:38:00 <tpbsd> what are you smoking ? can I have some
19:38:19 <tpbsd> stop using that word tristing website!
19:38:48 <tpbsd> ok 255, what 1/255 between enemies ?
19:39:00 <jsoft> wot
19:39:21 <tpbsd> Im still waiting ....
19:39:33 <tpbsd> where is my 255 binary character ?
19:40:11 <jsoft> the ASCII chracter set ends at 127
19:40:47 <tpbsd> thats true, because 127 = 7 bits !
19:40:58 <tpbsd> seeing a corelation now ?
19:41:21 <jsoft> I get it can be represented as 7 bits
19:41:54 <jsoft> The whole thing was terminal vs some other more generic uC to uC situation
19:42:10 <jsoft> And how Xon/Xoff worked.
19:42:20 <jsoft> OBviously it could only work in such a terminal situation
19:42:26 <tpbsd> thats true, but if i represent a m60 with a apple, that apple can hardly blow you to bits in a most satisfactory way now can it ?
19:43:13 <tpbsd> terminals always always use UARTS
19:43:43 <jsoft> Yes yes yes, but lets say a modem, or some gizmo where you are sending actual binary data.
19:43:46 <tpbsd> and usarts almost always use ascii
19:45:21 <tpbsd> if a modem is using 7 bit data, ie ASCII, then binary data can be sent, but must be ENCODED
19:45:56 <jsoft> n81 is not 7 bits though
19:46:03 <jsoft> ?
19:46:15 <tpbsd> thats what all those protocols ie KERMIT etc were, they just encoded binary over 7 bit ascii
19:46:23 <tpbsd> thats true
19:46:36 <jsoft> Hence all the confusion about all this 7 bit shit
19:46:40 <tpbsd> ahh
19:46:50 <tpbsd> maybe we use 8 bit ascii then
19:47:01 <jsoft> Right well ascii still works just fine on 8 bits
19:47:04 <jsoft> I get that
19:47:16 <tpbsd> that probablly explains all the extra graphics characters
19:47:28 <tpbsd> yeah, "man ascii"
19:47:55 <tpbsd> ok, we use 8 bit ASCII thesedays
19:48:05 <tpbsd> apologies, I was confused
19:48:19 <tpbsd> well some things probably use 7 bit ascii
19:48:23 <jsoft> Perhaps you need a slow cooked roast beef roll
19:48:26 <jsoft> :P
19:48:42 <tpbsd> Mecrisp-Stellaris for instance doesnt use any ascii that uses the 8th bit
19:49:01 <tpbsd> hot beef rolls with gravy .... yummmmmmmmmmmm
19:49:19 <jsoft> tpbsd, what values are Xon/Xoff?
19:49:29 <tpbsd> decima 17 and 19
19:49:33 <jsoft> ahhhh ok
19:49:34 <tpbsd> decimal
19:49:52 <tpbsd> so they live in the 7 bit ascii space
19:50:01 <jsoft> Right right
19:50:06 <jsoft> Ok that makes sense
19:50:15 <tpbsd> I worked in data comms for about 7 years and uses 7 bit ascii a lot
19:50:28 <tpbsd> back around 1985
19:50:48 <jsoft> I bet if you tried to talk to mecrisp with 7 data bits it would explode
19:51:00 <jsoft> on the serial side
19:51:13 <tpbsd> notr if I set the mecrisp usart to 7 bits :)
19:51:20 <jsoft> Well yes, yes this is true :P
19:51:41 <tpbsd> as it is I do a few mods to Mecrisp-Stellaris to make my serial comms work for me
19:51:56 <tpbsd> mainly up the speed and add hardware handshaking
19:51:59 <jsoft> But you get my confusion about all this, never used xon/xoff, and I hear 7 bits serial and im all 'duuuh what?'
19:52:12 <tpbsd> yeah, I do now, apologies
19:52:31 <tpbsd> mind you, what I said still applies to 7 bit ascii
19:52:41 <tpbsd> as regards xon/xoff
19:52:59 <tpbsd> in fact nothing changes 
19:53:00 <jsoft> like how it works?
19:53:04 <tpbsd> yeah
19:53:08 <jsoft> Yeah I get it now
19:53:47 <jsoft> I thought that you were talking serial comms, as in 0-255 data transfer, not just ascii based comms
19:53:53 <tpbsd> Im only working on xon/xoff as a simple alternative for new Mecrisp-Stellaris users
19:54:00 <tpbsd> aha
19:54:13 <jsoft> tpbsd, so have you finished the xon/xoff code?
19:54:34 <tpbsd> Mecrisp-Stellaris doesnt have a 8 bit data transfer mechanism over the terminal
19:54:53 <tpbsd> jsoft, no, thats next after i finish my revamped memstat
19:55:05 <tpbsd> jsoft, Ive partially finished it
19:56:09 <jsoft> Hmm
19:56:39 <jsoft> So the idea being things can go super fast and be all funky, similar to how your existing stop on error stuff works?
19:56:43 <tpbsd> jsoft, I've been unifying my main Forth development utility words to take parameters instead of file changes for different configs
19:57:59 <tpbsd> jsoft, exactly, but the emphasis is on simple reliable comms
19:58:20 <jsoft> Awww yep
19:59:09 <tpbsd> because most new users get stuck at the start, confused whenever mecrisp-stellaris 'locks up' on uploads 
19:59:37 <tpbsd> xon/xoff is a attempt to remove that obstacle
19:59:49 <jsoft> It locks up?
19:59:58 <tpbsd> yep
20:00:06 <tpbsd> you experienced it iirc
20:00:06 <jsoft> Hmm
20:00:24 <jsoft> Not that I recall
20:00:35 <tpbsd> you first used 'picocom' ?
20:00:39 <jsoft> no
20:00:50 <tpbsd> what ?
20:00:53 <jsoft> no
20:01:01 <jsoft> I used some windows based thing
20:01:13 <tpbsd> terraterm ?
20:01:17 <jsoft> Nah
20:01:24 <tpbsd> doesnt matter
20:01:28 <jsoft> Something which allowed uploading of files 'semi easily'
20:01:43 <tpbsd> did you ever upload files ?
20:01:51 <jsoft> I cant remember, but I thought 'fuck this, im going back to linux'
20:01:58 <jsoft> Yeah I was able to 'upload' files
20:02:01 <tpbsd> hahah, good choice
20:02:27 --- quit: Labu (Quit: Leaving.)
20:02:31 <tpbsd> what were your comms settings ?
20:02:48 <jsoft> n81, at 115200 or something
20:03:15 <jsoft> no flow control or anything
20:03:51 <tpbsd> end of line delay ?
20:04:07 <jsoft> no
20:04:19 <jsoft> It had some shit where it was looking for the right responses though
20:05:07 <tpbsd> which terminal application ?
20:05:17 <tpbsd> e4thcom ?
20:05:30 <jsoft> Thats what I use now. Nah it was something else
20:05:35 <jsoft> I cant remember osrry 
20:05:39 <tpbsd> ah i know
20:05:48 <tpbsd> that stupid jeelabs thing
20:05:56 <jsoft> it was shit though.
20:06:03 <tpbsd> yeah, GO based
20:06:10 <tpbsd> and unmaintained
20:06:21 <tpbsd> ah ok, I understand now
20:06:43 --- quit: proteus-guy (Ping timeout: 265 seconds)
20:06:52 <jsoft> Fuck perhaps I do have a tits memory
20:07:13 <tpbsd> i dont blame you in this case
20:07:47 <tpbsd> but yeah, terminal use with Forth has always been the *main* drama in my opinion
20:08:14 <jsoft> I dunno, I just googled stuff and eth4com or whatever its called came up, I tried that, and it was simple
20:08:15 <tpbsd> thats why rdrop-exit loves 'tethered forths' as they dont have a terminal
20:10:16 <jsoft> Hmm
20:11:41 <tpbsd> jsoft, excellent choice of e4thcom, thats why you never had any issues
20:12:15 <tpbsd> jsoft, but there is no e4thcom for windows so windows users suffer more, as usual
20:39:39 --- quit: WickedShell (Remote host closed the connection)
20:42:34 --- quit: ryke (Ping timeout: 258 seconds)
20:45:18 --- join: WickedShell joined #forth
21:10:16 --- quit: WickedShell (Remote host closed the connection)
21:38:08 --- join: gravicappa joined #forth
21:49:15 --- join: proteus-guy joined #forth
22:04:36 --- quit: iyzsong (Remote host closed the connection)
22:04:53 --- join: iyzsong joined #forth
22:26:53 --- quit: dys (Ping timeout: 265 seconds)
22:31:13 --- quit: irsol (Ping timeout: 250 seconds)
22:33:05 --- join: irsol joined #forth
22:49:15 --- quit: gravicappa (Ping timeout: 260 seconds)
23:37:26 --- quit: crab1 (Ping timeout: 268 seconds)
23:59:59 --- log: ended forth/20.01.10