Frank,

Great news. I had started the Parameter-Expansion module but got sidetracked by some real work ;-)

It's almost done but I'll need to do some more testing. I like your idea concerning the naming conventions with Parameter-Expansion. In fact, I implemented this already with CEE and will certainly add this to my code.

If you can wait a few days, then you don't need to code this feature.

>Ok, as always this is not getting along as fast as I hoped.
>The Editor kept me quite busy on the ALT-4 and my new CommentBlock-feature. When selecting complete rows via mouse or shift-down (shift-up respectively) the first character of the next row (row above) gets selected as well though not visible. Furthermore I do not get a clean CRLF at the line-end all the time (so far i've had CR only, LF only, CRCR and CRLF). That lead to funny (and less funny) results when commenting. I hope I have fixed that by now but please keep an eye on that when You use it later on.
>
>Intellisense / Foxcode obviously was never intended to be called from "outside" at all. However I needed that for the ALT-BACKSPACE-behaviour in order to force Expansion in the middle of a line. Luckily VFP comes with the sourcecode for that. However there must be a lot of foxcode-intelligence within VFP not provided / documented. All the stuff I found assumes that a foxCode-Object already does exist. In order to get this running at all I had do create a foxcodescript-Object and call it with itself.
>The FoxCodeScript-Object provides a method "ReplaceWord" that works quite well. Still it does not do anything, if the keyword is selected completely and it does not take care of the "~" - positioning either. So I had to rewrite this myself.
>I could have rewritten all the expansion-stuff by now but I wanted to make use of the foxcode-System.
>
>It's running now but if anyone out there is a real expert on this foxCode-stuff, any ideas and commends are highly appreciated.
>
>Now to the good things.
>I think I can post a first "beta" by tonight or maybe tomorrow. It will not have all the features in (I did not have a look on para-expansion yet), but commenting (ALT-4), CommentBlock, ForceExpansion (ALT-BACKSPACE), Localization (ALT-6) will be implemented so that You can get back to work <g>.
>
>Two more features, I want to implement and would like You comments on:
>
>DimDriver
>Do You, like me, hate writing array definitions?
>

>dimension la_Dummy[5, 2]
>la_Dummy[ 1, 1] =
>la_Dummy[ 1, 2] =
>la_Dummy[ 2, 1] =
>...
>

>And do you regularly get caught in the copy-paste-forgettochange-trap?
>
>Then You'll love my DimDriver. All You need is a "DIM"-expansion. It will ask for the array's name, rows and cols and returns and pastes the complete declaration.
>
>Inline sorting
>We do have several commands that have a comma separated list behind them. I have thought of: LOCAL, PRIVATE, PUBLIC, LOCAL ARRAY, PARAMETERS, LPARAMETERS and STORE TO.
>
>For theese You will have the ability to sort the following list alphabetically. A maximum line-length can be defined after witch the line will be broken to the next line.
>Line break can be either a ";" or a complete new paragraph with repetition of the initial command. If ";" is choosen You can specify whether the following lines should be indented by the length of the command.
>
>Thus this
>

>	LOCAL ln_RetVal, ln_SelStart, ln_SelEnd, ln_LocChars, ln_LocPos, ln_NewPos1, ln_NewPos2, lc_String
>

>
>could either become
>

>	LOCAL lc_String, ln_LocChars, ln_LocPos, ;
>	ln_NewPos1, ln_NewPos2, ln_RetVal, ;
>	ln_SelEnd, ln_SelStart
>

>
>or
>

>	LOCAL lc_String, ln_LocChars, ln_LocPos, ;
>	      ln_NewPos1, ln_NewPos2, ln_RetVal, ;
>	      ln_SelEnd, ln_SelStart
>

>
>or even
>
>

>	LOCAL lc_String, ln_LocChars, ln_LocPos
>	LOCAL ln_NewPos1, ln_NewPos2, ln_RetVal
>	LOCAL ln_SelEnd, ln_SelStart
>

>
>this will be customizable, so that the command and the first word to sort can be defined.
>
>
>Parameter-Expansion
>Most of us use naming conventions that implicitly indicate the vartype of a variable like ln_Count (local numeric) or tc_String (transferred character). Everyone does it differently but I think most of us do it the one or the other way.
>If I have to digg into this anyway, why not extend it so that the vartype is taken automatically from the variable? The only thing needed for flexiblity is either a property on the CEEClone-Object or a parameter in the script.
>
>
>
>That's it so far.
>
>Any comments will be highly appreciated.

Daniel