Win32 with ICU files build problem
I'm sorry if this is a repeat... I posted this accidentally to perl6-language... Following the instructions in README.Win32 (which has been successful for me in the past), no longer works successfully. First, I cannot run Configure.pl successfully; it complains about --icudatadir not being defined (again not one of the --icu* options mentioned in README.Win32 AND not necessary before). Defining --icudatadir, I now get the following error during make: Src\string_primitives.c(24) : fatal error C1083: Cannot open include file: 'unicode/ucnv.h': No such file or directory I had defined --icuheaders in my call to Configure in whose directory 'unicode/ucnv.h' does exist. Does this mean that Configure is ignoring --icuheader or --icuheader is ignored in the build of the file above? Has anyone successfully built Parrot on Win32 (MSVC 13.10.3077) recently? Mark Solinski
Anyone have success build parrot with VC7 (.NET 2003)?
Has anyone built Parrot with VC7 (.NET 2003)? How do I get around the MSDEV.exe (IDE) is now DEVENV.exe (IDE) with incompatible project files? First off, why is the Win32 build of Parrot using .DSW/.DSP files? Is this only because of the ICU distribution? Would it be worthwhile to convert these .DSW/.DSP build files to makefiles? I used to be able to build Parrot with VC7 almost everyday until the merger with the ICU code. Now I never been able to build since ICU integration (even when I used a pre-built ICU - it fails in one of the language builds). If this hasn't been done and it is deemed important to do, I would gladly take on/assist with this task. I am, however, not experienced in Config. Mark Solinski A fox knows many tricks, a hedgehog but one -- a good one. -- Archilochus
RE: Classes and metaclasses
Malte Ubl wrote: Dan Sugalski wrote: So, if I understand this right (and I may well not), when you instantiate a metaclass you get a class, and when you instantiate a class you get an object, and since anything you instantiate is an object anyway that means classes are objects. I'm not entirely sure if metaclasses are objects, but it seems to lack a certain amount of egregious symmetry if it doesn't. Meta classes break the every class has a super class-chain by inheriting from themselves. A natural meta class is the word noun. It describes a class of words and it is an instance of that class. In many languages like Squeak, this is not quite true. Classes are instances of Metaclass, and Metaclass is an instance of the Metaclass class, so the circular reference occurs in the instantiation hierarchy and not the inheritance hierarchy. So for some instance abc of the ABC class which inherits from Object, we have (instance hierarchy) abc - ABC - ABC class - Metaclass - Metaclass class - Metaclass (inheritance hierarchy (simplified from Squeak)) ABC - Object Metaclass - Behavior - Object Metaclass class - Behavior - Object In languages such as Squeak, Smalltalk and Actor, every class does not inherit from themselves. There are usually only two special classes, like Metaclass and Behavior. Metaclass instantiates the class of classes and in turn is an instance of one of its objects, the Metaclass class. Behavior is the superclass of all classes which in turn has Object as its Superclass. In this way, all objects are instances of classes which have Object as their superclass. Metaclasses are objects (in languages like Squeak, Smalltalk and Actor). Mark Solinski The fox knows many tricks. The hedgehog knows one. One good one. -- Archilochus
RE: Docs and releases
I'm also a shy lurker but would love to help in any way I can. I have twenty+ years experience in C/C++/OOP. Is there a reasonable place to start? Mark Solinski [EMAIL PROTECTED] [EMAIL PROTECTED]
