While the rules are not strictly defined, I consider the following two entries borderline, if not completely illegitimate. Their causing crashes cannot be considered bugs (anyone doing this sort of thing deserves, and probably expects, the consequence): sscanf(G,%m); # 14 characters, including return pointto(0); # 12 characters Here's a reduction of your idea: normal:%(-eval(%)); # 20 characters

Thanks. I see the triangle, but hadn't before, or at least never knew what it did.

I've reduced that to 12 characters.

With 14 characters I can cause Execution stopped: Stack limit reached. I'll reveal it later (it probably should be considered cheating). I use the emacs key bindings. I wish there were a binding for delete word right (M-d, in emacs).

Pretzel (pdf) is a package for generating pretty printers. It uses lex and yacc, with extensions, to define a lexer and parser. I've got most of the grammar working, but need to tweak it to work with angle-bracket rtable constructors. I'll then extend it to work with noweb. My rationale for stripping comments is that because, in the source, they are terminated by the end of the line, then they should be presented the same way in the formatted text. However, that usually causes problems because they will frequently extend past the right margin in the typeset code (one of my goals is to be able to typeset code in pages with narrow columns (say two column format). However, because I'm willing to substitute symbols for Maple operators, then I should also be willing to wrap the comment line (i.e., neither is valid Maple). That may cause some problems if the comments are actually commented-out code. For a noweb extension I wrote, I used the string `#!' to tell LaTeX to typset the rest of the line as LaTeX, otherwise as verbatim text; possibly I'll do something similar. Another possiblity is to strip inline comments but typeset standalone comments as LaTeX. However, in a noweb source file there are few stand-alone comments; instead they are usually just part of the documentation chunk.

A Knuthian effort!

A Knuthian effort!

I hadn't noticed, until now, the actual number. 714. A fitting goal. For those not familar with baseball, it was Babe Ruth's career home run total.

I hadn't noticed, until now, the actual number. 714. A fitting goal. For those not familar with baseball, it was Babe Ruth's career home run total.

It isn't dynamic control, per se, that is the issue, but rather the ability of a skilled user to extend and/or modify an existing package but without the source code. Previously that could be done. Now it isn't practical or even possible. I doubt that the loss is significant and am confident that it is outweighed by the increased robustness of the modular approach, however, there have been times when I wished I could tweak an existing procedure or add an export to an existing package. With the old (and ugly) table-based packages that could be done.

It isn't dynamic control, per se, that is the issue, but rather the ability of a skilled user to extend and/or modify an existing package but without the source code. Previously that could be done. Now it isn't practical or even possible. I doubt that the loss is significant and am confident that it is outweighed by the increased robustness of the modular approach, however, there have been times when I wished I could tweak an existing procedure or add an export to an existing package. With the old (and ugly) table-based packages that could be done.

Congrats on your 700th post and thanks for pursuing the wiki. It should be interesting.

Congrats on your 700th post and thanks for pursuing the wiki. It should be interesting.

I'm not sure what you mean by TEXT mode, however, the way to changes fonts in the Standard gui is with User > Format > Styles, select the appropriate paragraph or character style, and then edit its font selection. After doing this, you'll want to save your style. To do that, use User > Format > Manage Style Sets. There are help pages describing this, look under ?worksheets,documenting,styles

It would be useful to have a table/page listing Maples features by release. This seems a case where a wiki would be ideal---easy for someone to start, and convenient for others to fill in the details and update.