"I am getting off-topic, but since I have already written what follows, and
I think it is informative, I am leaving it there :-)"
Thats ok my question has been answered by Sven's first reply anyway, some
offtopic wont hurt
"Python is a rather large language, with a large number of quirks that nee
> On 13 Jan 2016, at 18:14, Dimitris Chloupis wrote:
>
> Why the Cog VM is mentioned in my documentation is no accident. There is
> another VM that is called Stackless VM or old VM that was the VM before Cog
> that had no JIT and its a VM we still use for platforms that Cog VM does not
> curr
Why the Cog VM is mentioned in my documentation is no accident. There is
another VM that is called Stackless VM or old VM that was the VM before Cog
that had no JIT and its a VM we still use for platforms that Cog VM does
not currently run like Raspberry Pi, Android and I think iOS too.
"But nowa
It does not make as big difference as you think it does. First of all VM is
an executable binary so its already in machine code format or else it would
not run. The difference between the interpreter is that with the
interpreter you already execute machine code without any need to generate
it while
> On 13 Jan 2016, at 16:27, Dimitris Chloupis wrote:
>
> "The virtual machine (VM) provides the environment where the Pharo system
> lives. It is different for each operating system and hardware architecture,
> and runs as a machine language executable in the operating system. It
> implements
> On Wed, Jan 13, 2016 at 4:58 PM Werner Kassens wrote:
>>
>> Hi Dimitris,
>> your formulation "...Pharo bytcode...and convert it to machine code..."
>> is insofar irritating to me as "convert it to machine code" would
>> suggest to me that a compiler is at work here. Davids "executing Pharo
>> by
On Wed, Jan 13, 2016 at 11:41 PM, Dimitris Chloupis
wrote:
> great explanation Ben thanks for sharing, I agree 100% .
On Wed, Jan 13, 2016 at 11:46 PM, Sven Van Caekenberghe wrote:
> I like Ben's version too. (It helps to be a native English speaker as well ;-)
> Please write more, Ben.
Thanks.
Yep, I think that Ben's version is even better and more balanced for a
newbie while informative enough over David's draft.
Cheers,
Offray
On 13/01/16 10:30, Ben Coman wrote:
Oh! I should have guessed there'd be more alternative suggestions and held back.
Anyway, its done now, so just pick out
Hi,
I like David's proposal. It strikes a good balance between newbie
friendly and detailed enough foundations (you don't learn Peano's Axioms
before learning to count).
Cheers,
Offray
On 13/01/16 09:27, David Allouche wrote:
Hey,
Since I just recently figured that stuff out, my perspecti
I like Ben's version too. (It helps to be a native English speaker as well ;-)
Please write more, Ben.
> On 13 Jan 2016, at 16:41, Dimitris Chloupis wrote:
>
> great explanation Ben thanks for sharing, I agree 100% . ISO files are
> popular file formats used by other VMs , like VirtualBOX unli
great explanation Ben thanks for sharing, I agree 100% . ISO files are
popular file formats used by other VMs , like VirtualBOX unlike pharo image
they are not a memory dump but rather a hard disk dump which is later
loaded in memory usually to emulate booting from a DVD or booting a HD drive
http
Oh! I should have guessed there'd be more alternative suggestions and held back.
Anyway, its done now, so just pick out what you like...
Now I tend to think of the Image as more than just the .image file, so...
The heart of Pharo is the *Image*. This holds the live running state
of a Pharo system
"The *virtual machine* (VM) provides the environment where the Pharo system
lives. It is different for each operating system and hardware architecture,
and runs as a machine language executable in the operating system. It
implements the details of managing memory, executing Pharo byte-code, and
com
Hi Dimitris,
your formulation "...Pharo bytcode...and convert it to machine code..."
is insofar irritating to me as "convert it to machine code" would
suggest to me that a compiler is at work here. Davids "executing Pharo
byte-code" seems more understandable to me here.
werner
On 01/13/2016 0
Hey,
Since I just recently figured that stuff out, my perspective might be useful.
I do not think it is a good idea to push external VCS too much at this point.
They are important to collaboration, so they should be mentioned, but they add
a lot of complexity.
Taking into account the feedback
Its an open book, if people dont like it , it can always been removed. Just
because I am most active , thats does not make me the boss. But yes I do
disagree that a simple explanation of what the VM really is should be
ommited, because for me that is just plain bad documentation to mention
somethin
> On 13 Jan 2016, at 14:22, Dimitris Chloupis wrote:
>
> I assume you have never read a an introduction to C++ then :D
I have and they are too complex.
> here is the final addition for the vm
>
> (Vm) is the only component that is different for each operating system. The
> main purpose of th
I assume you have never read a an introduction to C++ then :D
here is the final addition for the vm
(Vm) is the only component that is different for each operating system. The
main purpose of the VM is to take Pharo bytcode that is generated each time
user accepts a piece of code and convert it t
> On 13 Jan 2016, at 13:42, Dimitris Chloupis wrote:
>
> I mentioned bytecode because I dont want the user to see at some point
> bytecode and say "What the hell is that" I want the reader to feel confident
> that at least understands the basic in Pharo. Also very brief explanations
> about b
I mentioned bytecode because I dont want the user to see at some point
bytecode and say "What the hell is that" I want the reader to feel
confident that at least understands the basic in Pharo. Also very brief
explanations about bytecode I have seen in similar python tutorials.
Obviously I dont wan
Sounds about right.
Now, I would swap 1 and 4, as the image is the most important abstraction.
There is also a bit too much emphasis on (byte|source)code. This is already
pretty technical (it assume you know what compilation is and so on). But I
understand it must be explained here, and you did
So I am correct that the image does not store the source code, and that the
source code is stored in sources and changes. The only diffirence is that
the objects have a source variable that points to the right place for
finding the source code.
This is the final text if you find anything incorrect
> On 13 Jan 2016, at 10:57, Dimitris Chloupis wrote:
>
> I was adding a short description to the UPBE about sources file , I always
> thought that the sources file is the file that contains the source code of
> the image because the image file itself stores only the bytecode.
>
> However its
Le 13 janv. 2016 à 10:57, Dimitris Chloupis a écrit :
> I was adding a short description to the UPBE about sources file , I always
> thought that the sources file is the file that contains the source code of
> the image because the image file itself stores only the bytecode.
>
> However its j
I was adding a short description to the UPBE about sources file , I always
thought that the sources file is the file that contains the source code of
the image because the image file itself stores only the bytecode.
However its just came to my attention that the sources file does not
contain code
25 matches
Mail list logo
