Problem Report - newline character no longer works in a string

Works like a charm, also in previous Prime versions.

However, Mathcad will allow only codes up to 255, and produces an ellipsis "..." at the lower of the three:

Luc

I imagine one of two scenarios existed:

1.  Somebody saw I was using the feature and invoked the Bruff Exclusion Rule, whereby anything I find useful or want is excluded at the earliest opportunity.

2.  Somebody, a user, got confused.  So the feature was removed rather than, say, suggesting that they apply a filter to their string to remove any characters they didn't like.   (The latter would have been the better option, as people who do use the feature cannot apply a filter to restore the capability (but see Scenario 1)).

This has been the default go-to scenario since Mathsoft ran the show.  Tom Gutman introduced me to the term "Nannyware" to describe such an approach.  There was one particular Mathsoft change that had me gibbering and hooting like a demented chimp on a flinging spree - I wish I could remember what it was (well, OK, there have been multiple changes that have induced that behaviour in me, the current subject being another one).

The fact that Tab (09) functionality still exists suggests that a third scenario, fixed in a general clean-up, probably didn't happen.

For control codes that don't have a reasonable interpretation under a virtual document rendition, there are always the Unicode symbols:

A far more sensible approach, IMO, but what would I know?

Stuart

... Ah, yes.  A user complained that Mathcad crashed when running a recursive function that had no termination condition. So, instead of fixing the problem, Mathsoft added a recursion depth limit of around 4000, on the basis that who would ever want a recursion depth of more than that?  I mean, that would be silly.  Naturally, as one who regularly exceeded that depth, I whined like a whiny thing that had a special reason to whine (and I did have one).  The response?  Apparently, I could play with the Registry and set my own limit. 

Again, I howled, pleaded, and wheedled to get a proper fix, using the pathetic excuse that setting Registry values wasn't exactly portable and many organisations forbade users (or anyone!) from playing with the Registry upon pain of termination; for monsters could be summoned if the mages cast an improper spell upon the Registry.  Would it not be better, I urged, to fix the problem by at least keeping an eye on the stack, and educating users on the need to write correct recursive programs?

Last I looked, the recursion depth limit was still there.  Yep, still there at 4766.  A very annoying limit (especially for those who use Express, which isn't exactly a selling point).

Heck, we haven't even got mutual recursion as a consolation prize.

Still, somebody must have noticed that I did actually use the Registry fix for recursion depth - see Scenario 1; if it's still in the Registry, I can't find it.