Instead of producing an error, what do you think about what
CompiledMethod class>>#new?

Seems like if #new does that instead of erroring, maybe basicNew
should not error?

I remember needing to relax ContextPart class>>#basicNew: just a bit
so that the code could be more uniform.  Check it out.

Similar situation in this case -- we have a tool that wants to operate
at that level and makes assumption that basicNew should never fail,
which at least seems worthy to consider..

Your call, thanks!

On Sun, Feb 16, 2014 at 7:46 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Sat, Feb 15, 2014 at 06:52:18PM -0800, tim Rowledge wrote:
>>
>> Wasn?t there some change discussed a while ago that had something to do with some number class and #new? The 13297 image says
>> CompiledMethod>basicNew: size
>>
>>       self error: 'CompiledMethods may only be created with newMethod:header:?
>
> I should think that in addition to #basicNew: that we should also have protection
> against callng #basicNew
>
> CompiledMethod>basicNew
>
>         self error: 'CompiledMethods may only be created with newMethod:header:'
>
> Right?
>
> Dave
>
>