00:00:00 --- log: started forth/13.01.05 00:12:12 --- join: epicmonkey (~epicmonke@188.134.41.173) joined #forth 00:12:12 --- mode: ChanServ set +v epicmonkey 00:23:10 --- quit: Nisstyre-laptop (Ping timeout: 255 seconds) 01:17:19 --- join: regreg (~regreg@77.81.148.213) joined #forth 01:17:19 --- mode: ChanServ set +v regreg 02:10:39 --- quit: protist (Ping timeout: 255 seconds) 02:11:09 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 02:11:09 --- mode: ChanServ set +v MayDaniel 02:26:53 --- join: protist (~protist@125-237-130-19.jetstream.xtra.co.nz) joined #forth 02:26:53 --- mode: ChanServ set +v protist 04:32:39 --- quit: epicmonkey (Ping timeout: 265 seconds) 04:43:01 --- join: obobo_ (~chatzilla@dyn-dsl-pt-76-75-103-192.nexicom.net) joined #forth 04:43:01 --- mode: ChanServ set +v obobo_ 04:44:34 --- quit: obobo (Ping timeout: 245 seconds) 04:44:40 --- nick: obobo_ -> obobo 04:57:22 --- join: ncv (~quassel@89.35.216.197) joined #forth 04:57:22 --- quit: ncv (Changing host) 04:57:22 --- join: ncv (~quassel@unaffiliated/neceve) joined #forth 04:57:22 --- mode: ChanServ set +v ncv 04:59:24 --- quit: protist (Quit: Lost terminal) 05:10:52 --- join: protist (~protist@125-237-130-19.jetstream.xtra.co.nz) joined #forth 05:10:52 --- mode: ChanServ set +v protist 05:27:13 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 05:27:13 --- mode: ChanServ set +v fantazo 05:42:18 --- join: epicmonkey (~epicmonke@188.134.41.173) joined #forth 05:42:18 --- mode: ChanServ set +v epicmonkey 05:48:11 --- quit: tgunr_ (Quit: I'm outta here) 05:50:32 --- join: tgunr_ (~davec@cust-66-249-166-11.static.o1.com) joined #forth 05:50:32 --- mode: ChanServ set +v tgunr_ 06:37:15 --- quit: fantazo (Read error: Operation timed out) 08:10:39 --- quit: tgunr_ (Ping timeout: 260 seconds) 08:17:41 --- join: tgunr_ (~davec@cust-66-249-166-11.static.o1.com) joined #forth 08:17:41 --- mode: ChanServ set +v tgunr_ 08:21:41 --- join: Onionnion|Eee (~ryan@68.254.171.79) joined #forth 08:21:41 --- mode: ChanServ set +v Onionnion|Eee 08:28:12 --- quit: Onionnion|Eee (Quit: Leaving) 08:32:42 --- quit: tgunr_ (Ping timeout: 246 seconds) 08:37:18 --- join: tgunr_ (~davec@cust-66-249-166-11.static.o1.com) joined #forth 08:37:18 --- mode: ChanServ set +v tgunr_ 08:44:57 --- quit: protist (Ping timeout: 256 seconds) 08:48:49 --- join: protist (~protist@125-237-130-19.jetstream.xtra.co.nz) joined #forth 08:48:49 --- mode: ChanServ set +v protist 08:51:35 No, gforth 070 'see' has the issue.. I forget what I had before I installed lubuntu, but gforth used to "work" with code words as well 08:53:30 note, however - when it lokked up, ^D caused it to unseize, dump hex, and continue 08:54:24 --- quit: protist (Ping timeout: 246 seconds) 08:56:02 --- join: protist (~protist@125-237-130-19.jetstream.xtra.co.nz) joined #forth 08:56:02 --- mode: ChanServ set +v protist 09:46:01 --- quit: mark4 (Quit: brb switching wm) 09:48:09 --- join: mark4 (~mark4@240.sub-70-194-73.myvzw.com) joined #forth 09:48:09 --- mode: ChanServ set +o mark4 10:09:33 --- quit: mark4 (Remote host closed the connection) 10:11:23 --- join: mark4 (~mark4@240.sub-70-194-73.myvzw.com) joined #forth 10:11:28 --- mode: ChanServ set +o mark4 10:13:12 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 10:13:12 --- mode: ChanServ set +v fantazo 10:18:45 --- quit: fantazo (Quit: leaving) 10:23:52 --- join: _spt_ (~in@host-92-12-211-132.as43234.net) joined #forth 10:23:52 --- quit: _spt_ (Changing host) 10:23:52 --- join: _spt_ (~in@unaffiliated/-spt-/x-5624824) joined #forth 10:23:52 --- mode: ChanServ set +v _spt_ 10:24:42 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 10:24:42 --- mode: ChanServ set +v fantazo 10:59:00 slackers 11:26:24 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 11:26:28 --- mode: ChanServ set +v Nisstyre-laptop 11:34:09 --- join: Onionnion|Eee (~ryan@adsl-68-254-171-79.dsl.milwwi.ameritech.net) joined #forth 11:34:09 --- mode: ChanServ set +v Onionnion|Eee 11:34:25 So, I'm curious.. Has anyone started using forths with gui's, applications, or microcontrollers? 11:40:33 ? 11:41:00 pick almost any micro controller you can think of and thers probably a forth for it 11:41:14 you will have difficulty finding forth implementations for some pic's tho 11:41:21 but pic's are not worth using anyway 11:41:59 so you say, I'm still curious who is using a forth and where.' 11:43:11 the entire fedex tracking system was developed by forth inc 11:43:30 the robotic arm simulator for the space shuttle was coded in forth but the arm itself wasnt 11:43:39 Cool! That wasn't what I asked, however ;-) 11:43:50 when i worked for vertex rsi in longview texts all of their products were forth 11:43:56 they make satellite tracking systems 11:44:04 Neat. 11:44:09 for direct tv, the military and a number of astronomical observatories 11:44:20 tho. they were bought by general dynamics and might not use forth any more 11:55:48 --- quit: mark4 (Ping timeout: 252 seconds) 11:56:30 --- join: mark4 (~mark4@240.sub-70-194-73.myvzw.com) joined #forth 11:56:30 --- mode: ChanServ set +o mark4 12:07:07 --- quit: fantazo (Ping timeout: 240 seconds) 12:10:05 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 12:10:05 --- mode: ChanServ set +v fantazo 12:10:37 --- quit: epicmonkey (Ping timeout: 272 seconds) 12:24:07 --- join: RodgerTheGreat (~rodger@71-13-215-242.dhcp.mrqt.mi.charter.com) joined #forth 12:24:07 --- mode: ChanServ set +v RodgerTheGreat 12:50:59 --- join: obobo_ (~chatzilla@dyn-dsl-mb-216-168-124-99.nexicom.net) joined #forth 12:50:59 --- mode: ChanServ set +v obobo_ 12:53:10 --- quit: obobo (Ping timeout: 264 seconds) 12:53:22 --- nick: obobo_ -> obobo 13:05:43 --- quit: Nisstyre-laptop (Quit: Leaving) 13:05:53 --- quit: Nisstyre (Quit: Leaving) 13:11:59 --- quit: Bahman (Quit: No Ping reply in 180 seconds.) 13:12:26 --- join: Bahman (~Bahman@2.146.91.136) joined #forth 13:12:26 --- mode: ChanServ set +v Bahman 13:15:16 --- quit: regreg (Remote host closed the connection) 13:16:08 --- quit: protist (Quit: leaving) 13:40:54 --- quit: fantazo (Read error: Operation timed out) 14:05:34 --- quit: _spt_ (Quit: power failure .. socket error) 14:19:54 --- join: ncv_ (~quassel@89.35.216.197) joined #forth 14:19:54 --- mode: ChanServ set +v ncv_ 14:33:14 --- join: Nisstyre (~yours@oftn/member/Nisstyre) joined #forth 14:33:14 --- mode: ChanServ set +v Nisstyre 14:46:17 --- quit: Onionnion|Eee (Quit: Leaving) 14:53:30 about that gforth 'see' issue, could you try this fix : http://pastebin.com/ApFLYyQ3 ? 14:55:42 see. any time people post patches as a fix to forth i cringe 14:56:19 if they wrote it right the first time, we'd not need fixes 14:56:21 in fact i cringe at patching like this in ANY language 14:57:11 wouldnt it be nice if every single package manager supplied DIFFS for every single update we did on our system? 14:57:20 what an awesome world it would be then 14:59:15 --- quit: ncv_ (Remote host closed the connection) 15:01:22 and yet, patching is bad - you just said so ;-) 15:01:40 yes it is 15:01:52 give me something i can read and evaluate 15:02:15 not rediculously unreadable patch file 15:02:39 but then. i think pretty much all of gforths sources are unreadable anyway 15:02:51 so i guess in this case it wouldnt help to post sources 15:03:00 but then gforth isnt forth either 15:04:20 well, gforth launches gdb to do the dissassembly, and there's a syntax error in the script passed to gdb, so it waits for input after printing an error message sent to /dev/null by gforth, hence the freeze. 15:05:10 the gdb command 'disas' needs a comma between the two memory adress arguments 15:06:55 that is a better description but gives me one more reason to hate on gforth. shelling out to a GNU development tool 15:06:57 lol 15:08:21 I can appreciate leveraging every tool on yer platform, but dumb is dumb. THe script should have been in a config file. 15:11:06 --- quit: MayDaniel (Read error: Connection reset by peer) 15:12:40 mark4: in what sense is gforth not a forth? 15:12:58 * PoppaVic pops popcorn.. 15:15:04 --- join: Onionnion|Eee (~ryan@adsl-68-254-171-79.dsl.milwwi.ameritech.net) joined #forth 15:15:04 --- mode: ChanServ set +v Onionnion|Eee 15:15:54 "the ans forth standard does not describe the forth language but a language of the same name" 15:16:09 and gforth is written in C. any "forth" that is written in C is NOT a forth by any stretch of the immagination 15:16:12 not now, not ever 15:16:27 I disagee, but carry on ;-) 15:16:32 who said that? 15:16:35 gforth is a horrendously complex pile of bloated horse shit 15:16:43 who said what 15:16:47 THAT I believe I will agree with 15:16:48 the "ans forth standard... " ? 15:16:52 that would be chuck moore 15:17:30 who by the way was ON the initial ans standards team but got up and walked out in frustration 15:17:53 I'll give you that gforth is bloated, but it obviously incorporates most of the features and properties of a forth (plus a bunch of other crap) 15:18:22 thats like saying MS windows incorporates most of the features and properties of a stable, secure operating system 15:18:53 I think you're taking an unnecessarily hard line here 15:19:06 against bloated horseshit? lol yes. 15:19:14 bloated OVERLY complex horse shit 15:19:22 forth is not bloated 15:19:24 forth is not complex 15:19:38 gforth is not forth on 2 counts and either one of them will instantly disqualify it 15:20:37 forth is also never written in c 15:20:50 right. Forth is FIG forth and all your other bitches are invalid! 15:20:57 * PoppaVic chortles 15:21:16 what forth would you recommend for linux ? and why ? I noticed gforth is 'large' 15:21:21 compared to gforth figforth is a masterpiece of beauty and engineering 15:21:21 It just reeks of redefining terms to suit you. There is a lisp-weenie troll who prowls this channel occasionally who frequently asserts that things are "not a proper forth". Forth is a toolbox of ideas and a way of thinking as much as it is a language. 15:21:37 carc im the author of isforth 15:21:48 rog:this is me - Just Smilin' ;-) 15:21:58 but as im the only one working on it and as nobody else ever will i guess i cant recommend it 15:22:07 there are some issues that im slowly working to resolve 15:22:22 too much of GForth is written in C, but C is as acceptable a language for bootstrapping a forth as any 15:22:34 no its not 15:22:37 not everything has to be metacircular 15:22:40 the only acceptable one is FORTH 15:22:44 gforth is a really complete, large imp - way overkill in some ways. Demonstrative in others. Not really any "exemplary" forth 15:23:15 PoppaVic: being widely available does provide some utility 15:23:21 how about we all boot to windows and launch a linux launcher app and have that bootstrap us into linux 15:23:38 that is a nonsensical comparison 15:23:40 I disagree. Forths were almost always born from an asm file of primitives, and the supportive secondaries sources 15:23:53 gforth is intended to be the golden standard forth compiler 15:24:03 I don't get that impression 15:24:11 100% in compliance with a standard you cannot wholy be incompliance with 15:24:18 it's supposed to be "complete" and portable 15:24:45 I think gforth was indeed intended to be a "standard implementation", but fails in several ways - useful, it remains.. So are pforth, ficl, and PFE 15:25:23 i think i pissed off the author of ficl in the early days of this channel and i dont think he ever came back 15:25:40 gforth like ALL c code. is bad example code 15:26:01 having to wade through 500 gigs of C sources to learn forth... how is someone going to learn forth 15:26:06 ever 15:26:20 best way to learn Forth is to write a Forth 15:26:24 learning forth does not mean knowing dup drop nip swap tuck 15:26:26 sorry, be advised they used C to write their engine and VM-whatever thingie, to compile and run gforth - it's not even a good example of a C-based forth. 15:26:27 that's why we have a million of them 15:27:00 no we have a million of them because they are so simple to create when you know the language 15:27:07 which you will NEVER learn using gforth 15:27:08 not ever 15:27:17 well, at least ficl added vocabularies.. I can't even stomach the idea of a forth w/o vocs, order, also only 15:27:36 isforth does not have also 15:27:38 or order 15:27:50 yes, and I don't use it 15:28:32 I suppose you hate JonesForth as well because it is written in x86 assembly 15:28:32 also seems kinda stupid to me. its as if you had to do a DUP before you could push any new items onto the parameter stack 15:28:40 because all new items overwite the top item 15:28:49 yes, I agreethe voc "words 15:29:04 no. jonesforth is written in forth using assembler primitives and macros to compile the forth 15:29:05 " are quite odd, but once you use them they sorta' work. 15:29:17 but jonesforth has other issues 15:29:30 the rot/-rot thing 15:29:36 isforth's kernel is written in nasm assembler. but the output of nasm is identical to what a metacompiler would produce 15:30:42 isforths kernel will remain a nasm based source tree until i get the x86 assembler i have never been able to create in over 10 years fnished 15:30:54 well. that and a metacompiler but metacompiler is trivial once i have the assembler 15:31:00 ideally you should be able to implement a forth in "asm" (which is never portable) as C (which theory sez is portable). 15:31:22 PoppaVic, NO code is ever portable 15:31:26 unless its trivial code 15:31:42 And, metacompilers are cute: there are multiple metacompilers and NONE are readable and fewer are "portable". 15:31:43 show me any portable non trivial code and ill show you 284658729 different unreadable interleaved versions of it 15:32:01 c could be portable except you'd have a hell of a time writing programs which exercised no undefined behavior 15:32:05 i4: and yet, you claimed FIG was bad for being a single assembler file. 15:32:06 PoppaVic, meta compilation is not that different from normal compilation 15:32:16 meta compiling is just target compiling 15:32:50 PoppaVic, it was bad for not being factored. factoring is not just at the function block level. its at the file level too 15:32:56 I've multiple books/refs around and can re-read metacompiling ideas at will - it's not readable or really portable. 15:33:08 blobbing every single source file for openoffice or mozilla firefox into a single file would be doable too! 15:33:38 FIG was written in the early days of uselessnet - a single file is easy. 15:33:47 but compared to gforth fig forth was a masterpiece 15:34:00 easy and wrong 15:34:35 gon look up the light table ide - its not something i will ever use but it has an even finer refinement of this idea 15:34:44 I do recall a shitload of argument/debate over FIG and F79 and F83 in the Forth Dimensions during that era.. I found most of the arguments esoteric/mathematical/theory. 15:35:23 I dunno lighttable, or ide. 15:35:26 PoppaVic, of the 3 i only ever used 83. 15:35:52 light table is an ide - thers a video of it, watch the vid. its really interesting what that guys doing 15:36:02 oh, I used all of them.. The big changes seem to have been do/loop and some number shit, and the entire state-smart-is-evil thing 15:36:09 not that im interested in using it or touting it for use... but its still interesting 15:36:34 state smart is not evil at all. thats just utter limp wristedness from the ans committe 15:36:48 they also re-broke NOT 15:37:03 actually they deleted NOT because the 83 standard had the audacity to FIX not 15:37:08 and we cant have that! 15:37:14 everyone use "invert" !!! 15:37:15 brb 15:37:16 it wasn't just the ANSI commies.. The german guy - I forget the name - was ready to "prove" the evil over and over 15:39:07 ok am i here? my cell phone had to be docked and docking it always disconnects my wifi tether 15:39:15 hahaha 15:39:19 ok im here 15:39:29 "sone germina guy" 15:39:42 I can never recall his name.. 15:39:45 i use state smart. state smart is a TOOL and a very VERY useful one 15:40:02 --- join: nal (~nal@173.215.251.14) joined #forth 15:40:02 --- mode: ChanServ set +v nal 15:40:20 You'll find every forth has to use state-smart in a few places.. Yet no one else should be allowed ;-) 15:40:33 : const create , immediate does> @ ?comp# ; 15:40:40 the ?comp# makes it state smart 15:40:50 it says. compile this constant as a literal or return it 15:40:51 state smart words are a nice simple way to make primitive words inline themselves among other things, but they can also make some kinds of metaprogramming more difficult 15:40:55 for shame! you looked behind the curtains! 15:41:23 RodgerTheGreat, err no thats a HORRIBEL way to do that lol 15:41:32 Yes. I will agree state-smart words can eat your face (let alone bite yer ass off). 15:41:34 : blah postpone x postpone y postpone z ; 15:41:40 isforth has a currently borken 15:41:52 m: foo lots of forth code here ;m 15:41:56 eww - I loathe that postpone junk 15:41:59 : blah .... foo .... ; 15:42:04 and foo will be inlined 15:42:18 not sure why its currently broken but it is. i have to fix it :) 15:42:36 but 0 const foo makes foo a state smart IMMEDIATE word :) 15:42:48 2 counts against const in the eyes of the ans committee 15:42:50 I have to wonder - I may be alone - if it would be better to fork the dictionary with compile-only/visible to the left and interpret-only/visible words to the right. 15:43:03 my var and const are how i think variable and constant should have worked from day 1 15:43:15 what ans calls a (camp voice) value i call a var 15:43:23 I'd say value and variable are "better" than constant 15:43:26 the name value does not express that the "value" is a variable 15:43:44 0 const zero 15:43:48 : blah .... zero .... ; 15:44:06 there will be a "(lit). 0" compiled into the definition for blah 15:44:11 since a Value is a constant until you change it, I see it more closely similar to #define/#undefine 15:44:11 a LITERAL is a constant 15:44:15 a constant in forth is not 15:44:28 depends on the implementation 15:44:42 I agree with the way you've defined it 15:44:43 fight! fight! figh! 15:44:48 heh 15:44:54 that's how it works in my forth 15:45:10 i have variable, i have constant but i use var and const in my code 15:45:16 when i want a constant to be constant i use const 15:46:18 so presumably your issue with constant is that it typically has runtime behavior and loads from a cell in the parameter field 15:46:19 I think using space and time to FETCH a constant is half-witted 15:46:21 instead of inlining 15:46:54 i dont have that issue with it :) 15:47:01 tho... i can see it could be an issue 15:47:16 then could you clarify? 15:47:16 PoppaVic, what about in C. where you have a const string. thats got to be fetched 15:47:39 i have no GRIPE with variable and constant, i just think their definitions are WRONG. 15:47:56 : variable create , does> @ ; or the equiv asm of coruse or 15:48:14 : constant create , does> @ and compile a literal or return a value here ; 15:48:24 thats how variable and constant should have been defined from the get-go 15:48:46 i4: in C, a "string" is compiled somewhere regardless; assigning char *p=string; sets a value just like char c[]="string" copies it. 15:48:54 they wernt defined that way so i created var and const as alternatives to them 15:50:42 ok, notethat "variable" will just leave the address on the stack; "constant" will perform the fetch. Both allocate the same space. 15:51:14 yes and ' blah >body will get the address of either 15:51:48 yeah, I forget how exactly "Value" works, but it is both and neither 15:52:03 ' constant alias value 15:52:06 think of it that way 15:52:23 the definition for value is identical to the definition for constant 15:52:37 but because its name does not imply that it is constant its ok to modify it 15:52:53 value was implemented because people were doing 10 constant my-var 15:53:11 well, again: think define/undef 15:53:14 because thers no associated fetch required on my-var and stores can be done with !> 15:53:23 totally different 15:53:31 no, it isn't but ok 15:53:35 #defines are macros. they exist at compile time only 15:54:29 yes, and in forth a constant is compiled; and a value can be adjusted (like redefine), and - well, it may be that time is different in C and forth. 15:54:58 C has a clean split between "compile time" and "run time" 15:55:09 forth doesn't (which is actually quite useful) 15:55:22 compile time IS run time 15:55:30 :) 15:55:32 yes 15:56:04 : ask ," do you want sugar in your coffee" get-answer !> answer ; 15:56:07 ask forget ask 15:56:07 rog: I agree forth confuses them, doesn't make them les true. 15:56:23 it doesnt confuse them 15:56:38 I will certainly conceed that cpp is run before C compiles, however 15:57:19 the limited expressive power of C is beneficial to portability mainly because it makes it impossible to do the sorts of clever tricks you can do in forth 15:57:25 worse-is-better 15:58:20 forth is an exposed breadboard, C is a circuit-breaker 15:58:53 don't get me wrong, I strongly dislike C 15:59:05 * PoppaVic chortles 16:00:58 RodgerTheGreat, i like yu :) 16:01:03 you 16:01:06 ok 16:01:11 pervert ;-) 16:01:14 i also hate c 16:02:55 need to reboot 16:03:00 --- quit: mark4 (Remote host closed the connection) 16:04:29 Funny.. I don't ;-) 16:04:51 insert joke about women and bathrooms 16:14:27 one could argue that C is very much like JavaScript 16:14:40 a lingua franca we didn't ask for, but that perhaps we deserve 16:14:42 please.. my tummy.. 16:16:44 RodgerTheGreat: As do I, C sucks 16:16:59 Long live Factor 16:17:17 if only Factor were self-hosting 16:17:45 although as I have said before, Forth could be a fine language for implementing the factor runtime ("VM") 16:18:08 How do you mean: self hosting? 16:18:47 well, factor relies on some runtime services which are written in C++ - the GC, for example 16:19:21 Ah, yes the kernel depends on C 16:19:43 *most* of Factor is written in Factor, but it's not totally self-sufficient 16:19:46 --- join: mark4 (~mark4@240.sub-70-194-73.myvzw.com) joined #forth 16:19:46 --- mode: ChanServ set +o mark4 16:20:06 I'll just wait for SPECTRE 16:20:44 do tell 16:21:04 Hey, I flew on SPectre! :) 16:21:41 AC-130 in the 16th SOS 16:22:34 iirc, the AC130 had a big fat barrel sticking out the left side. 16:23:04 wrong spectre, however. (xref sean connery and 007 ;-) 16:23:33 you flew the c130? 16:23:46 Actually, we had 10 barrels sticking out 16:24:03 yeah, 133 missions 16:24:14 ive climed all over c130's i was a crewchief lol 16:24:23 awesome! Salute! 16:24:27 tactical aircraft maintainace specialist 16:25:04 Awesome bird, lost the #2 engine one night 16:25:20 on sheppard afb thers a b52 with a twisted airframe. the plonker flying it wanted to know if a b52 could do a barel roll 16:25:21 it can 16:25:27 but it cant fly again sfter 16:25:36 yea c130 can fly on one engine 16:25:44 ha ha, Also flew as tail gunner on B52 :) 16:25:54 lol 16:26:16 we called the F4 a fod bucket 16:26:33 actually any aircraft can do an aileron roll, barrel roll is different 16:27:16 yep, worked as a weapon mech on F4, F102, A1E, and A26 among others 16:27:28 the aircraft i worked on was the OV10A Bronco 16:27:48 Loaded those at NKP, we had 2 squadrons of OV-10 16:28:21 Use them for spotters with the Calif Dept of Forestry now 16:28:27 someone put the empenage control surfaces back on using the wrong bolt. the pilot was ordered to bail but he refused. he used his ailerons and rudeer to gain the altitude he needed to get over the mountains and home safe 16:28:39 he got a high 5 and a severe chewing out for not bailing out lol 16:28:52 should have gotten a DFC! 16:29:11 if they were airforce ov10's they were my squadron. but the marines fly them too 16:29:16 but they fly the Bs 16:29:32 Heard of Pardo's push? 16:29:43 http://www.historynet.com/pardos-push-an-incredible-feat-of-airmanship.htm 16:29:44 newp 16:31:24 Awesome feat of airmanship 16:39:26 wow thats some story 16:42:03 yes it is, they had a play on on an episode of JAG 16:42:10 on it 16:42:32 Rab, pushes an F-18 out of Iraq 16:43:04 At the time I said, no -way but at the end of the show they mentioned Pardo's push 16:43:43 heh 16:44:02 How long were you in? 16:44:19 even with heavy aircraft losses they should never have repremanded those guys. thats FOUR live pilots and 2 dead planes 16:44:26 84 to 87 16:46:19 cool, 67-77 here, medically retired :( 16:46:28 loved my flying job 16:46:46 anytime you get paid to fly is a good thing :) 16:48:42 i never got to FLY lol 16:49:56 got my pilot license in '73, instrument rating in '97 16:51:48 you were talking about barrel rolls earlier, Tex Johnson did one in a 707 which help sell the AC to the USAF 16:51:51 http://www.youtube.com/watch?v=Ra_khhzuFlE 16:52:19 Actually an aileron roll 16:57:12 --- quit: nal (Ping timeout: 252 seconds) 17:06:10 ive done no coding in 2 days because instead of coding ive been fighting alsa to get it to FUCKING play sound out my HDMI 17:06:39 * PoppaVic chuckles 17:08:55 --- join: nal (~nal@173.215.251.14) joined #forth 17:08:55 --- mode: ChanServ set +v nal 18:05:29 --- quit: ncv (Remote host closed the connection) 18:22:07 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 18:22:07 --- mode: ChanServ set +v Nisstyre-laptop 19:18:19 https://www.youtube.com/watch?v=jxodluTaz4g <-- does this work for anyone all the way thru? 19:18:38 it keeps crapping out on me afger about 45 seconds of play 19:24:56 No idea. Filled out another online app.. Tick-tock. 19:26:41 i4: btw, a friend took me on a trip yesterday.. I've discovered Mecca.... 19:26:48 Frye's electronics ;-) 19:27:09 Now, all I need is a similar gunshop - I can die with a blissful smile ;-) 19:32:54 lol frys electronis is good! 19:33:09 but you want to LIVE with one lol 19:33:56 I just want to win a shopping-spree.. Give me a day to plan my run, a non AAA basket, and get the hell outa the way! ;-) 19:35:25 I wonder if they got top-end solderstations with multi tips and hotair as well... scopes.. meters... chips! and more chips!! 19:36:36 PoppaVic, dont get one form them 19:36:41 you will only see weller 19:36:45 ugh 19:36:48 go to www.adafruit.com and look under tools 19:36:53 and get the one they sell. i bought it 19:36:57 its VERY VERY good 19:36:57 well, I'll just the basket with OTHER goodies! ;-) 19:37:04 unfortunately im not lol 19:37:34 I found an even nicer unit via amazon with both types of pen. I just can't afford it ;-) 19:38:55 http://www.adafruit.com/products/303 19:38:57 i have that 19:39:01 brb 19:41:32 i also have a dso quad but the user interface makes it next to unusable 19:42:47 mark4: I'm not having any trouble with that video 19:43:02 damn i hate my usb tehter 19:43:17 http://www.adafruit.com/products/788 <-- i also want these.. for those SPECIAL occasions :))) 19:43:34 http://www.amazon.com/REWORK-SOLDERING-IRON-STATION-handles/dp/B004ZB9D4O and http://www.amazon.com/Updated-Aoyue-Digital-Soldering-absorber/dp/B006FA481G/ref=pd_cp_hi_2/181-5338072-2746435 (latter is almost what I found earlier this year) 19:46:17 mark4: those are neat but extremely bloody expensive 19:50:53 yea lol thats shy i dont have them 19:51:04 she makes them with a lazer cutter i believe 19:51:56 but she also does solder flow in a skillet using an arduino and a motor and a tem sensor to do the temperatur profiling to get a good solder joint 19:52:02 she has a video of this lol 19:54:29 oh i guess she doesnt make them 19:56:36 the video in this page of the girl doing lock picking is misleading 19:57:05 pins on tumbler locks like that are waisted. they have a little waist on the upper and lower pins to stop you from being able to pick them easilly 20:01:16 --- quit: nal (Quit: Leaving) 20:01:58 This is why the gods created acids.. and liq. nitrogen. 20:02:13 and leg muscles and sholders 20:03:23 and 12ga doorbusters ;-) 20:03:48 ..I am NOT risking hip, or threatening my shoulder/knee with a replacement. 20:22:24 --- quit: Nisstyre (Read error: Connection reset by peer) 21:42:26 PoppaVic: I have one of those stations, works geeat 21:42:50 looks like it should 21:43:33 First one crapped out, but they sent a replacement right away and been good since, 5 years ago now 21:44:14 ccool 22:06:43 --- quit: mark4 (Quit: Leaving) 22:49:01 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 22:59:05 --- join: regreg (~regreg@77.81.148.213) joined #forth 22:59:05 --- mode: ChanServ set +v regreg 23:43:38 --- quit: Onionnion|Eee (Quit: Leaving) 23:54:05 --- quit: regreg (Remote host closed the connection) 23:59:59 --- log: ended forth/13.01.05