Variable names in #abtBuildInternals

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Variable names in #abtBuildInternals

Louis LaBrunda

Hi All,

Is it just me or would anyone else like the variable names in the auto generated code in #abtBuildInternals to be less close to what I choose when I want to add an instance variable to the class?  Here's what happens.  When the code for #abtBuildInternals is generated, local variables are needed and therefor generated.  The names relate to the part being put in the *window*.  This is nice to a point, if you look at the generated code you can easily tell what is what.  The trouble starts when for whatever reason you want to add an instance variable to the *window*.  I seem to often choose the same name chosen by the code generator of #abtBuildInternals.  Saving the object definition with the new instance variable causes #abtBuildInternals to fail to compile.  Tweaking and saving the *window* causes #abtBuildInternals to be regenerated with variables that don't conflict but it doesn't get saved correctly.  You get the following warning:

Warning: 65 The edition of TheClassName>>abtBuildInternals you just replaced is not the released one, which is Undefined.

A little playing around fixes that, if you remember to do it.

I think it would be very nice if the variables generated for #abtBuildInternals were just a little different (maybe a few extra characters designed to eliminate or at least reduce the conflicts).  Maybe starting with "x" or "abt" or anything that most of us wouldn't use as part of an instance variable name.

Lou

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Variable names in #abtBuildInternals

Richard Sargent
Administrator
+1
The temp variable names are highly readable, but do steal the namespace.

On Wednesday, July 2, 2014 7:39:46 AM UTC-7, Louis LaBrunda wrote:

Hi All,

Is it just me or would anyone else like the variable names in the auto generated code in #abtBuildInternals to be less close to what I choose when I want to add an instance variable to the class?  Here's what happens.  When the code for #abtBuildInternals is generated, local variables are needed and therefor generated.  The names relate to the part being put in the *window*.  This is nice to a point, if you look at the generated code you can easily tell what is what.  The trouble starts when for whatever reason you want to add an instance variable to the *window*.  I seem to often choose the same name chosen by the code generator of #abtBuildInternals.  Saving the object definition with the new instance variable causes #abtBuildInternals to fail to compile.  Tweaking and saving the *window* causes #abtBuildInternals to be regenerated with variables that don't conflict but it doesn't get saved correctly.  You get the following warning:

Warning: 65 The edition of TheClassName>>abtBuildInternals you just replaced is not the released one, which is Undefined.

A little playing around fixes that, if you remember to do it.

I think it would be very nice if the variables generated for #abtBuildInternals were just a little different (maybe a few extra characters designed to eliminate or at least reduce the conflicts).  Maybe starting with "x" or "abt" or anything that most of us wouldn't use as part of an instance variable name.

Lou

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/d/optout.