> > > If you have some way of uniquely identifying a method, then you
> > > can put the source wherever you like (e.g., in some other live
> > > object memory), and look it up when you need it. For an example,
> > > see the MethodID class in Spoon[1].
> >
> > indeed.
> > it is really unimportant w
On 19 February 2012 13:37, Igor Stasenko wrote:
> On 19 February 2012 00:54, Craig Latta wrote:
>>
>> Hi--
>>
>> If you have some way of uniquely identifying a method, then you can
>> put the source wherever you like (e.g., in some other live object
>> memory), and look it up when you need it
On Sun, Feb 19, 2012 at 2:37 PM, Igor Stasenko wrote:
> On 19 February 2012 00:54, Craig Latta wrote:
> >
> > Hi--
> >
> > If you have some way of uniquely identifying a method, then you can
> > put the source wherever you like (e.g., in some other live object
> > memory), and look it up whe
On 19 February 2012 00:54, Craig Latta wrote:
>
> Hi--
>
> If you have some way of uniquely identifying a method, then you can
> put the source wherever you like (e.g., in some other live object
> memory), and look it up when you need it. For an example, see the
> MethodID class in Spoon[1].
>
Hi--
If you have some way of uniquely identifying a method, then you can
put the source wherever you like (e.g., in some other live object
memory), and look it up when you need it. For an example, see the
MethodID class in Spoon[1].
-C
[1] http://dl.dropbox.com/u/15188004/spoon/Spoon%203%
On 18 January 2012 10:22, Igor Stasenko wrote:
> On 17 January 2012 19:22, Mariano Martinez Peck wrote:
>>
>>
>> On Tue, Jan 17, 2012 at 6:31 PM, Mariano Martinez Peck
>> wrote:
>>>
>>>
If you don't bother about being slow, you can also make it much easier:
|trailer source m
On 17 January 2012 19:22, Mariano Martinez Peck wrote:
>
>
> On Tue, Jan 17, 2012 at 6:31 PM, Mariano Martinez Peck
> wrote:
>>
>>
>>> If you don't bother about being slow, you can also make it much easier:
>>>
>>>
>>> |trailer source m |
>>> m := (Gofer>>#load).
>>> trailer := m trailer.
>>> sou
On Tue, Jan 17, 2012 at 1:40 PM, Mariano Martinez Peck
wrote:
>
> 2) I can understand to put source code in files would make sense 20 years
> ago. But I don't think so anymore... a normal notebook has 8gb of RAM these
> days.
I believe the Windows VM still limits us to around 1/2 gig of image
siz
On Tue, Jan 17, 2012 at 1:40 PM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:
>
> Well, with the following script it seems I am able to embed all source
>> code in trailers:
>>
>> | trailer source key dict classes |
>> dict := IdentityDictionary new.
>> CompiledMethod allInstances do: [:
On 17 Jan 2012, at 22:40, Mariano Martinez Peck wrote:
> 1) From a design point of view, I think that CompiledMethodTrailer is the
> correct place where source code should be stored.
Why?
From my point of view, the source fits into the image, but does not belong into
the CompiledMethod.
Comp
> Well, with the following script it seems I am able to embed all source
> code in trailers:
>
> | trailer source key dict classes |
> dict := IdentityDictionary new.
> CompiledMethod allInstances do: [:aMethod |
> trailer := aMethod trailer.
> source := aMethod getSource.
> trailer so
On Tue, Jan 17, 2012 at 6:31 PM, Mariano Martinez Peck <
marianop...@gmail.com> wrote:
>
> If you don't bother about being slow, you can also make it much easier:
>>
>>
>> |trailer source m |
>> m := (Gofer>>#load).
>> trailer := m trailer.
>> source := m getSource.
>> trailer sourceCode: source.
12 matches
Mail list logo
