Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #35999

Re: Don't be a bit-twiddling monkey

Show all headers | View raw

On Sat, 24 Jan 2015 11:42:08 -0500, Julian Fondren  
<julian.fondren@gmail.com> wrote:

> KMP: You are inquiring about something for which there is a
> lot known, and about which you can learn a lot, but it won't
> get you closer to "understand closures".
>
> Likewise, you can find exchanges in clf where one person will
> say "I'm implementing a forth so that I can better understand
> Forth" and people will point out that this is not exactly a
> direct route.

As one in that position, it's more like "I'm implementing a forth
and I'm learning forth along the way, even though I don't care to
learn that much about forth" and people here will point out that
you don't need to understand how forth works in order to program
in forth therefore learning how forth works is useless. Which,
I think is somewhat absurd ...  At least, that's my grasp on what
others here have tendency to say.

> Meanwhile, my Forth-on-CGI project has hit a speed bump that
> would benefit greatly from some bit twiddling (that I cannot
> provide):

I'm assuming that neither of the two issues below have anything
to do with your "Forth-on-CGI".  I'm assuming you mentioned them
because you're looking for alternate method to bypass the
"speed bump" in your forth.  Is that correct?  Or, is your
"Forth-on-CGI" coded for Swiftforth or GForth?

> 1. SwiftForth is a 32-bit Forth.  My webhost uses a 64-bit
> Linux - and consequently, 64-bit libraries, such as the
> libraries you must use to communicate with MySQL or SQLite.
> SwiftForth can't use those libraries.

I'm not familiar with Swiftforth.

What do you mean by "can't use"?  I.e., what is the actual problem?
Why can't Swiftforth use those libraries?

E.g., I could assume that you mean you "can't use" the libraries
because they're 64-bit and Swiftforth is 32-bit and you don't know
how to use 32-bit values to create 64-bit values.  Or, I could
assume that may SwiftForth doesn't have an FFI to the libraries.
But, as to which assumption, if either, is correct, I can't tell.
Of course, one can make many other assumptions too.

> 2. I have a 64-bit Gforth build, but its FFI involves
> compilation and those tools (libtool, gcc, etc.) aren't
> available, so I can't use those libraries with it either.

Ok.

> I've fallen back to using popen2 with 'mysql' (the binary).
> The overhead of this method makes PHP more competitive, so
> I'm also having to stop and consider a variety of DB-less
> alternatives.

It seems popen2() is listed as deprecated.  Should you be using it?
https://docs.python.org/2/library/popen2.html

My I assume your "Forth-on-CGI" is coded in Python?  I.e., since
you're using popen2() ...

If so, what is the actual "speed bump"?  ISTM, you haven't actually
mentioned it yet ...  I.e., if you mention it, maybe someone here
can help.

If not, i.e., coded for Swiftforth or GForth, how did you get access
to an FFI for Python without the tools to compile?  e.g., built-in?
Does Python have other FFIs built-in?  e.g., to access C?


Rod Pemberton

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Don't be a bit-twiddling monkey "WJ" <w_a_x_man@yahoo.com> - 2015-01-24 01:14 +0000
  Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-23 20:55 -0500
    Re: Don't be a bit-twiddling monkey Jason Damisch <jasondamisch@yahoo.com> - 2015-01-24 07:52 -0800
      Re: Don't be a bit-twiddling monkey Julian Fondren <julian.fondren@gmail.com> - 2015-01-24 08:42 -0800
        Re: Don't be a bit-twiddling monkey Paul Rubin <no.email@nospam.invalid> - 2015-01-24 09:10 -0800
        Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-24 14:57 -0500
          Re: Don't be a bit-twiddling monkey Julian Fondren <julian.fondren@gmail.com> - 2015-01-24 14:32 -0800
            Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-25 01:37 -0500
              Re: Don't be a bit-twiddling monkey Julian Fondren <julian.fondren@gmail.com> - 2015-01-24 23:32 -0800
                Re: Don't be a bit-twiddling monkey Bernd Paysan <bernd.paysan@gmx.de> - 2015-01-25 21:23 +0100
          Re: Don't be a bit-twiddling monkey "Elizabeth D. Rather" <erather@forth.com> - 2015-01-24 21:22 -1000
            Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-25 17:52 +0000
              Re: Don't be a bit-twiddling monkey anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-01-26 14:15 +0000
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-26 19:59 +0000
                Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-28 22:30 -0500
              Re: Don't be a bit-twiddling monkey albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-01-26 18:24 +0000
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-26 19:58 +0000
                Re: Don't be a bit-twiddling monkey "Elizabeth D. Rather" <erather@forth.com> - 2015-01-26 11:27 -1000
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-26 21:52 +0000
                Re: Don't be a bit-twiddling monkey "Elizabeth D. Rather" <erather@forth.com> - 2015-01-26 18:01 -1000
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-27 10:47 +0000
                Re: Don't be a bit-twiddling monkey foxaudioresearch@gmail.com - 2015-01-27 19:08 -0800
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-28 12:06 +0000
                Re: Don't be a bit-twiddling monkey Lars Brinkhoff <lars.spam@nocrew.org> - 2015-01-28 13:18 +0100
                Re: Don't be a bit-twiddling monkey Michael Barry <barrym95838@yahoo.com> - 2015-01-28 08:14 -0800
                Re: Don't be a bit-twiddling monkey Lars Brinkhoff <lars.spam@nocrew.org> - 2015-01-28 18:53 +0100
                Re: Don't be a bit-twiddling monkey Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2015-01-28 22:14 +0000
                Re: Don't be a bit-twiddling monkey Lars Brinkhoff <lars.spam@nocrew.org> - 2015-01-29 08:14 +0100
                Re: Don't be a bit-twiddling monkey empty-buffers <empty.buffersYOU-DONT-WANT-THIS@gmail.NEITHER-THIS.com> - 2015-01-29 00:21 +0000
                Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-28 20:05 -0500
                Re: Don't be a bit-twiddling monkey Coos Haak <chforth@hccnet.nl> - 2015-01-29 03:33 +0100
              Re: Don't be a bit-twiddling monkey Bernd Linsel <bl1@gmx.com> - 2015-05-09 02:15 +0200
            Re: Don't be a bit-twiddling monkey "Rod Pemberton" <buzz@notnotnontnooatno.cmm> - 2015-01-25 17:35 -0500
        Re: Don't be a bit-twiddling monkey Bernd Paysan <bernd.paysan@gmx.de> - 2015-01-25 00:37 +0100
          Re: Don't be a bit-twiddling monkey "Elizabeth D. Rather" <erather@forth.com> - 2015-01-24 21:08 -1000
        Re: Don't be a bit-twiddling monkey anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-01-25 15:36 +0000
      Re: Don't be a bit-twiddling monkey Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2015-01-26 17:24 +0100
  Re: Don't be a bit-twiddling monkey hughaguilar96@gmail.com - 2015-01-23 21:56 -0800

csiph-web