[M3devel] _lowbits / _highbits (Pixmap bug-- 4.1 vs. buggy 5.x)

[Randy Coleburn]

Olaf / Jay:
 
My Reactor v4.1 CD has a source directory, but this folder does not
contain the sources for the compiler or Reactor, just the libraries et
al.
 
Here is a list of the archives in that folder:
 
BINUTILS.TGZ
m3-comm.TGZ
m3-db.TGZ
M3-DEMO.TGZ
M3-GAMES.TGZ
M3-LCTRN.TGZ
m3-libs.TGZ
M3-MAIL.TGZ
M3-OBLIQ.TGZ
M3-PKGTL.TGZ
M3-TOOLS.TGZ
m3-ui.TGZ
m3-www.TGZ
M3CC.TGZ
M3GDB.TGZ
 
There is also a CONTRIB folder with the following:
 
CVSUP
IDLM3
M2TOM3
M3DDD
M3PC
M3TOMIF
SRC-M3
 
If Farshad is ok with it, I can send you these files, but I would need
his approval because we licensed this product from Critical Mass.
 
On a side note, I just built a new laptop computer from a fresh install
of XP Pro.  I got the latest cm3 from the repository and rebuilt
everything.  On this platform, my pixmaps show up with a "yellow" color
everywhere "white" would normally show.  This is strange behavior.  I
checked the .lst file and it is showing as a GUI program and the
"hand.obj" is included.  Any ideas?
 
Since Jay has made good progress on fixing some of my major gripes, I
am trying to use the new (current) cm3 for my project that is due for
delivery at the end of July.  The new garbage collector seems to work
much better on Windows than the one from 4.1.  Since we don't have an
official stable release right now, I am going to have to draw a line in
the sand at some point soon and take a snapshot of the cm3 source tree
as the "official" development environment for future support of my
project deliverables.
 
This latest problem with pixmaps on one platform and with CM3IDE on all
XP platforms I've tested so far is disturbing.  As soon as I can get a
handle on these problems, I think I am going to freeze my development
environment for this project unless someone comes up with a major
fix/change.
 
Regards,
Randy

>>> Olaf Wagner <wagner at elegosoft.com> 5/29/2008 9:02 AM >>>
Quoting Jay <jayk123 at hotmail.com>:

> 1) Just fyi, NT386GNU didn't build with my fix, so it is disabled   
> there only, and the bug could very well be present there.
> Er, then again, this stuff works differently for the gcc backend, so 

>  I don't know, I'll have to look, and run the tests, not today.
> Which reminds me also, these symbols should be static hand.c, except 

>  for NT386 -- the source can't tell, so it'll have to be a define   
> from the m3makefile.
>
> 2) Can anyone confirm my history and the missing source?
> ie: Confirm that what is marked as 4.1 and 5.1 in CVS really is 4.1  

> and 5.1? I don't think 4.1 is accurately marked.
> In particular, I don't think the 4.1 Stackx86.m3  is what 4.1   
> actually shipped.
>
> 3) Or confirm my analysis that leads to the "accusation"? It was
tedious.

I don't think that a complete 4.1 code set was ever imported into
the CVS CM3 repository; at least I don't remember we got the complete
4.1 code from Farshad Nayeri. What we got was 5.1 and it wasn't even
compilable by any existing M3 compiler. The gcc backend was so old
that it wasn't usable on any system we had. I think we extensively
used
PM3 for booting and even incorporated some of PM3's code where
necessary.

I remember that I had several evaluation CDs from CM3 some years
before
the open source release, so it may be that contents from one of these
CDs were imported as 4.1. I'm afraid it is not really traceable now.
We never got any versioned code from Critical Mass (I don't know what
they used for version control), only the bare source code.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin,
Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45
86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz:
Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
DE163214194


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080529/2d672f00/attachment-0002.html>