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

Groups > comp.lang.forth > #58788

Re: gforth and shared libraries

From Andreas Klimas <klimas@w3group.de>
Newsgroups comp.lang.forth
Subject Re: gforth and shared libraries
Date 2017-05-07 22:27 +0200
Organization A noiseless patient Spider
Message-ID <oenvp4$8ha$1@dont-email.me> (permalink)
References <oei3tg$6e4$1@dont-email.me> <oei6du$fpu$1@dont-email.me> <2017May6.182411@mips.complang.tuwien.ac.at> <oemmqp$jr$1@dont-email.me> <2017May7.120327@mips.complang.tuwien.ac.at>

Show all headers | View raw

On 2017-05-07 10:03:27 +0000, Anton Ertl said:

> Andreas Klimas <klimas@w3group.de> writes:
>> What I really want to do is to mmap a shared file for persistent storage,
>> like block but without the need of the word update. Maybe
>> is it possible to make a direct systemcall (int 80) ?.
>> I'm not planning to use any C code because I want to
>> cut the requirements for a c-compiler.
> 
> Sure it's possible.  I would not do it, though.  If you have the
> current development version of Gforth, you can use unix/mmap.fs, and
> because the generated C code is compiled while Gforth is built, so you
> don't need a C compiler at run-time.

unfortunately the current development version didn't compile on my Mac
and I don't want to investigate work in this direction.
Using readily working development systems (like SwiftForth, Smalltalk
or Racket Scheme, only to name a few) is a big benefit for me.

the reason for using gforth is to get the binary without the need of
an installed C compiler. I'm working on different computers and
operation systems (Mac, Linux, Windows) and I don't want,
or even can't, install a C development toolchain. But I can scp or
ftp a simple exe-file.  So call me a bit lazy.

> 
> As for not needing UPDATE, yes that happens automatically with mmap,
> but you still need to msync or munmap to make sure the data is written
> back to persistent storage.  And if the system crashes between your
> changes and the msync()/munmap(), the persistent state may contain
> some changes, but not necessarily all of them, and you don't know
> which changes you get and which not.

a long time ago we talked about the same topic (in using mmap) and you
told me the same argument. well, now, 10 years later, I'm using this method
with a great success and have never lost any data. It is just simple and
fast. very different to our SQL-Server experience (in speed and
reliability).
a systemcrash nowadays is very seldom. Our internet server has
a few years uptime.

thank you for your response
Andreas Klimas

> 
> - anton

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

Thread

gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-05 17:01 +0200
  Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-05 17:44 +0200
    Re: gforth and shared libraries anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-06 16:24 +0000
      Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-07 10:48 +0200
        Re: gforth and shared libraries anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-07 10:03 +0000
          Re: gforth and shared libraries albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-07 13:40 +0200
          Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-07 22:27 +0200
            Re: gforth and shared libraries Bernd Paysan <bernd@net2o.de> - 2017-05-07 23:57 +0000
              Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-08 10:44 +0200
                Re: gforth and shared libraries anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-08 11:26 +0000
                Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-08 17:08 +0200
            Re: gforth and shared libraries pahihu <pahihu@gmail.com> - 2017-05-09 10:31 -0700
              Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-10 09:40 +0200
        Re: gforth and shared libraries albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-07 13:37 +0200
          Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-07 22:50 +0200
            Re: gforth and shared libraries minforth@arcor.de - 2017-05-07 14:41 -0700
              Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-08 10:49 +0200
                Re: gforth and shared libraries minforth@arcor.de - 2017-05-08 02:16 -0700
                Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-08 16:32 +0200
                Re: gforth and shared libraries minforth@arcor.de - 2017-05-08 08:00 -0700
                Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-08 17:52 +0200
                Re: gforth and shared libraries minforth@arcor.de - 2017-05-08 09:33 -0700
                Re: gforth and shared libraries anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-09 15:44 +0000
                Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-10 09:51 +0200
                Re: gforth and shared libraries anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-10 10:16 +0000
                Re: gforth and shared libraries Andreas Klimas <klimas@w3group.de> - 2017-05-10 12:31 +0200
                Re: gforth and shared libraries albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-10 12:51 +0200

csiph-web