Re: [Prothon-dev] new python

We need to move this to prothon-user since we've decided hypothetical
discussions belong there.

I don't understand your "4th dimension" idea immediately, but then the 4th
dimension is hard to grasp :)  I assume you use the term 4h dimension as in
time being the 4th dimension of physical space.  Obviously dimensions don't
mean much in object space.

I'm all for the idea of building in functionality at the object level, as
long as it is very basic and high-performance.  For example, I have an
archived bit in the object that is cleared whenever an object is
write-locked that I intend to use for persistent storage later.  I intend
for our basic pickling facility to offer serious object-oriented-data-base
features.

If you have thought it out this far, maybe you could give some kind of
example of an event that the object time facility could detect and/or
provide to the code?

----- Original Message ----- 
From: "Dennis Heuer" <[email protected]>
To: <[email protected]>
Sent: Friday, March 26, 2004 8:01 AM
Subject: [Prothon-dev] new python


> Interesting starting point. I myself, as I began learning python, got
> the feeling that there should be a python 2, cleaning up the rough edges
> and missing features and keywords. Hope, prothon will come close to my
> ideas :)
>
> I am currently programming a server/client-solution. Every time I have
> to fiddle around with parallel processes, timeouts, blocking vs.
> non-blocking and so on, I wished a language that has threading and 4th
> dimension implemented into the objects. I didn't read all the info about
> prothon yet but found a note about multithreading being a main scope of
> the interpreter. So, I'll concentrate on the 4th dimension.
>
> I find that programming languages are not aware of the existence of a
> fourth dimension. They offer simple routines like time.time() or even a
> small sceduler. But, dealing with time in a more complex fashion is not
> possible straight away. Most programming languages provide function
> calls like select. however, even select is only functional to some
> degree. It can wait for already established connections but it cannot
> wait for a connection being established. If I deal with FIFO's, for
> example, the opening of the FIFO blocks the whole program untill another
> process connects to the other end of the FIFO. The select function
> doesn't help me in this case because it first acts after the both
> processes are already connected. This is one of those examples where
> programmers must decide between blocking and waiting or non-blocking and
> driving circles with a while procedure or the like.
>
> I think, having a combination of timer and sceduler chained to every
> type, object and function/class/method can make a great deal. One could
> create scedulers, waiting calls, checking routines, queues,
> synchronizers etc. without fiddling with special function calls, modules
> and missing functionality here and there and for this and that.
>
> What do you think about implementing the 4th dimension into the objects
> and types?
>
> Dennis
>
>
> _______________________________________________
> Prothon-dev mailing list
> [email protected]
> http://lists.prothon.org/mailman/listinfo/prothon-dev
>
>
>
>


_______________________________________________
Prothon-user mailing list
[email protected]
http://lists.prothon.org/mailman/listinfo/prothon-user