El mié, 03-09-2008 a las 13:00 +0200, Andreas Barth escribió: > * José L. Redrejo Rodríguez ([EMAIL PROTECTED]) [080903 11:11]: > > El mar, 02-09-2008 a las 22:59 +0200, Andreas Barth escribió: > > > Package: squeak-vm > > > Version: 3.10.3+svn1902.dfsg > > > Severity: serious > > > > > > Hi, > > > > > > the file platforms/unix/src/vm/interp.c starts with: > > > > > > /* Automatically generated from Squeak on an Array(9 May 2008 11:24:03 am) > > > by VMMaker 3.8b6 [...] > > > > > > However, I cannot identify the source file for that file. > > > > "This" is the source file. Squeak people uses a Squeak image to store > > the virtual machine sources, as any other people can use svn o cvs. That > > message only means that the text file has been generated that way, but > > that file is the only and real source file to be compiled. > > So, I can load that text file from within squeak, and do any changes > there, and safe again? (i.e. that text file is the file actually used > for modifications?) >
Yes, these are the needed steps: - Open a Squeak standard image (as an example you can use the etoys package in non-free, that image is olpc'ed (thought to teach and learn) so it's not very confortable to use it to program but you might use it. - Install inside this image, using the Squeak Package loader the package VMmaker. - Start VMMaker and config it telling the path to the sources you want to modify, for example the sources from the Debian package - Modify the sources inside Squeak to do any change - Use VMMaker to regenerate the sources. If you don't use vmmaker you can do it manually, but it's harder due to the size of the sources, and the need of manually modifying some of the code depending on the plugins you're going to compile. Smalltalkers use the Squeak Image to modify the code, usually the plugins [1]. Ian Piumarta, the main author of the unix virtual image port, does it manually using a standard text editor for part of the code, excepting the plugins. He uses to program them inside the image, as it's easier to debug them in real time. A latest note: when modifying the code inside the image instead of using a standard text editor, the code is modified in "Slang" (C with Smalltalk syntax), that's how smalltalkers do it to use the same Smalltalk class browser. It does not matter if you use a plain text editor or Squeak to modify the code: at the end of the process VMmaker makes the translation to plain C. Obviously VMmaker is free and its sources (in Smalltalk) are available inside the same Squeak image. Regards. José L. [1] In Squeak plugins are functions that're executed by the virtual machine instead of by the image. That's usually done by perfomance reasons as all the code inside the image is in Smalltalk, and some actions very OS related are faster in C (i.e. accesing the filesystem, keyboard or the sound card)
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
