Python 1.2 beta 3 compiling problems + many other questions

Mark Oliver (moe@io.org)
9 Apr 1995 16:08:55 GMT

I've compiled Python v1.2 beta 3 on an Intel machine under the UNIX platform called QNX and
everything works great. However, when I change the options in the general Makefile to choose
compiling using 16 bit instead of 32 and a Large memory model instead of the default which is
small, the executable which is made fails its tests (make test).

Now I know that this begs the question 'Why would you compile 16-bit?'. Well, I'm evaluating
Python as a possible macro language for our product and I need to link it to a 16 bit interface
library. This isn't a MUST but if I choose 32 bit then I'll have to make an intermediate task
which will convert the messaging between 32 and 16 bit so that both sides will be happy.

Another question I have is that I'd like to use the '@' character. I've read the python doc's
and it blatently states not to, but our software uses variable of the sort :

object.attribute.value

where value can be @float, @integer, @string, @time, @date, etc.

Am I going to be able to get our variables into Python without a nomenclature change? Also,
these variable in our software are being held in a constantly updating database. Will I be able
to setup Python functions to execute based on passed exceptions or will I need to create an event
loop which will poll for changes? I haven't noticed any timers (although I haven't looked too
hard) in Python. What's the story here, since I'd also like to do some timed events?

Okay, I know there are a lot of questions here and much of it may be very specific to what I'm
trying to do so I'd be REALLY appreciative of any responses I can get.

Thanks

-- 
/////////////////\\\\\\\\\\\\\\\\\
          Mark D. Oliver
     Technical Services Manager
Comdale Technologies (Canada) Inc.
/////////////////\\\\\\\\\\\\\\\\\