00:04:34
##forth
<cleobuline>
xentrac: it's difficult becauof the big int pointers
00:05:29
##forth
<cleobuline>
for your idea i have tu suppress le word VARIABLE
00:13:27
##forth
<cleobuline>
i will look at this feature tomorrow , because i am stoned a this time xentrac
00:14:17
##forth
<xentrac>
haha
01:34:38
##forth
<cleobuline>
!gforth : SUM_SQUARE 1 + 0 DO I + LOOP DUP * ; 10 SUM_SQUARE .
01:38:11
##forth
<cleobuline>
!gforth : SUM_SQUARE 1 + 0 DO I + LOOP DUP * ; 0 10 SUM_SQUARE
01:38:21
##forth
<cleobuline>
!gforth : SUM_SQUARE 1 + 0 DO I + LOOP DUP * ; 0 10 SUM_SQUARE .
01:38:21
##forth
<gforth_eval_bot>
3025
01:45:42
##forth
<cleobuline>
!gforth : SUM_CUBES 1 + 0 DO I CUBE + LOOP ; 0 10 SUM_CUBES .
01:47:04
##forth
<cleobuline>
!gforth : CUBE DUP DUP * * ; : SUM_CUBES 1 + 0 DO I CUBE + LOOP ; 0 10 SUM_CUBES .
01:47:05
##forth
<gforth_eval_bot>
3025
01:47:28
##forth
<cleobuline>
marvelous :)
13:50:39
##forth
<cleobuline>
ForthBot: CREATE FOO 100 ALLOT
13:50:52
##forth
<cleobuline>
ForthBot: 123 5 FOO !
13:51:03
##forth
<cleobuline>
ForthBot: 5 FOO @ .
13:51:13
##forth
<cleobuline>
content xentrac ?
15:00:28
##forth
<crc>
user51: many years ago, I had written a thing in sed & shell scripts that translated forth to x86 assembly (it made use of some of the primitives from retroforth 6 or 7 IIRC)
15:00:50
##forth
<crc>
I had used it to write some small kernel modules for Linux back in 2002 or 2003
15:02:07
##forth
<user51>
crc: I wasn't even programming that time. :)
15:04:12
##forth
<crc>
I've been programming since 1996 or 1997, and using forth since 1998
15:04:29
##forth
<KipIngram>
I was just starting to USE Linux back around that time. I put it on a system so I could install open source (free) PCB layout software for consulting work. I do recall that Linux was still somewhat rough around the edges in those days.
15:04:52
##forth
<KipIngram>
I started programming in 1982 or so.
15:05:04
##forth
<KipIngram>
In college.
15:09:30
##forth
<user51>
I've been using Linux for 10 years and I'd still say it's rough around the edges.
15:14:16
##forth
<crc>
I started with MS-DOS, Oberon System 3, Linux (a stripped down Slackware), and Windows 3.1 on an old 80386. I've used lots of other OSes since then, but mostly use OpenBSD & FreeBSD these days.
15:14:45
##forth
<crc>
I picked up use of Linux & later BSD systems within a year or so of starting to use computers
15:20:12
##forth
<user51>
Coming from a Windows background, 98->XP->7, in Linux I always feel a bit of tension between the CLI and GUI.
15:27:36
##forth
<crc>
I don't do much with GUI stuff on my dev machine. I run X11 on occasion, mostly just to test little things or examine photos.
15:39:45
##forth
<crc>
a quick update on my konilo-over-irc bot: I've successfully tested it with three concurrent users, each with a separate ilo instance, per-user output cached to a file accessible via http. I still need to setup the per-user blocks, write some documentation, and do a lot more testing, but it's coming along.
16:37:01
##forth
<cleobuline>
ForthBot: : ? @ . ;
16:38:28
##forth
<cleobuline>
ForthBot: VARIABLE X 1234 X ! X ?
16:38:29
##forth
<ForthBot>
1234
16:39:32
##forth
<vms14>
I guess the first program I wrote was python
17:59:29
##forth
<KipIngram>
Aside from that calculator that was my actually "first platform," the first programming I did was in Fortran.
18:00:07
##forth
<thrig>
a (bad) dice roller in basic for an apple //e
18:01:42
##forth
<KipIngram>
pgimeno: Pretty quickly after that Fortrran course I followed up with Pascal and also with 6809 assembly.
18:02:03
##forth
<KipIngram>
I really found the 6809 to be elegant and pleasing.
18:02:12
##forth
<xentrac>
Yeah, everybody loves the 6809.
18:02:34
##forth
<xentrac>
Unfortunately when I had access to a CoCo I didn't know what assembly language was
18:02:55
##forth
<xentrac>
so I did lots of graphics demos, but they were all in BASIC.
18:41:53
##forth
<cleobuline>
alors les amis , vous allez bien ,
18:42:18
##forth
<cleobuline>
ForthBot: SEE SUM_SQUARE
18:42:19
##forth
<ForthBot>
: SUM_SQUARE 1 + 0 DO I + LOOP DUP * ;
18:57:35
##forth
<veltas>
The first proper programming I did was with C++
19:03:55
##forth
<vms14>
btw I have betrayed you all and made a lisp interpreter instead :D
19:04:25
##forth
<xentrac>
yay
19:05:13
##forth
<vms14>
I really tried hard to make the rpn abomination useful, but never was useful for more than a hello world
19:06:05
##forth
<vms14>
it was extremely complex to do even a single task
19:06:31
##forth
<user51>
I don't really think about forth as RPN anymore -- just as something that parses a string and executes the appropriate word.
19:06:37
##forth
<vms14>
all the overhead you avoid on the interpreter by using rpn and the stack, you put it on the programmer
19:06:56
##forth
<user51>
vms14: Code for your RPN abomination?
19:07:10
##forth
<vms14>
I guess the main problem was not having memory
19:07:32
##forth
<vms14>
that's one version in js
19:07:57
##forth
<vms14>
and that's what it does
19:08:15
##forth
<vms14>
you can move with wasd
19:08:36
##forth
<vms14>
the enemies just follow you, so they are friends instead
19:10:52
##forth
<user51>
That could be a start for something like Vampire Survivors.
19:10:52
##forth
<vms14>
that's exactly what it was xd
20:56:19
##forth
<crc>
running for a single user is a lot simpler; with this I need to consider more in terms of sharing resources & potential security issues
21:02:14
##forth
<crc>
vms14: one thing to remember here is that I'm not using any kind of bot scaffold; I have to deal with everything in the IRC protocol that's needed for this, so there's nothing like Bot::BasicBot to hide the details
21:12:27
##forth
<vms14>
yeah
21:12:45
##forth
<vms14>
in my case it was more as a proof of concept to test interoperability with perl modules
21:13:09
##forth
<vms14>
as that module requires you to subclass it and override the methods
21:17:25
##forth
<vms14>
s/as/since/
21:24:14
##forth
<crc>
When I'm done with this, I might do implementations in a few languages (retro, c, and python). It'd be interesting to see what differences or similarities arise as a result.
21:28:53
##forth
<vms14>
I wonder why don't you make web applications with retro ported to js
21:34:17
##forth
<KipIngram>
crc: I bet that will show some interesting things. I won't surprise me at all if the language tends us toward specific algorithms.
21:34:33
##forth
<KipIngram>
"It"
21:35:11
##forth
<crc>
vms14: I have zero interest in developing with js or doing modern web applications
21:35:43
##forth
<vms14>
well if it wasn't for the latter, the first might be the reason to have retro in js
21:36:00
##forth
<vms14>
which I guess you already have because I saw lots of implementations in several langs
21:37:15
##forth
<crc>
Honestly, at this point I mostly use Konilo for mg personal computing, and Retro when doing bigger tasks that need to interface more with a host system.
21:39:02
##forth
<crc>
(That's less common in the last couple of months; I have a lot of programs written in retro that just keep on working and fill their roles nicely.)
21:45:50
##forth
<crc>
I don't use any of these often. It's just wasteful to run X11 and a browser to run something that doesn't need any of this.
21:52:56
##forth
<vms14>
my goal is to make games with it so I can just throw links into people faces and they can start playing without installing anything, since everyone has a js powered browser
21:53:29
##forth
<vms14>
like that neocities link I gave before
22:55:59
##forth
<cleobuline>
ForthBot: WORDS
22:55:59
##forth
<ForthBot>
SUM_SQUARE ? X