Re: Variable length/precision formats?



robin wrote:
James Giles wrote in message ...
....
The feature requires something like "thunks" that change
the format as the I/O list is processed.

Well, then you implemented it wrongly, because the format
can be updated PRIOR to the passing control to format
processing.

The usual definition of the feature *requires* that the user
be allowed to change the format *while* the I/O list is being
processed. Yes, the user *should* avoid that like the plague.
It would be easier to avoid if it weren't possible in the
first place. The usual definition of the feature should be
changed so that it's impossible to have the format change
during the processing of the I/O list. It's the worst aspect
of the feature.

The value of the
format changes every time one of the variables used
in any of the VFEs in the format string gets changed. This
includes changes made to those variables on-the-fly: *WHILE*
the I/O list is being processed. Variables such as implied
loop indices and I/O list items themselves can be in the
VFEs!

They don't have to be, as I pointed out in an earlier post.

The *implementation* must permit them to be (by the usual
definition). The *user* should probably avoid doing so.
The usual definition of the feature should change so that the
*implementation* no longer even needs to support the capability.

The instances in this newsgroup are primarily with basic uses,*
not those doing anything remotely like what you described.
Just f<w>.<d>

But, for *those* instances, the ability to change W or
D *during* the processing of the I/O list is particularly
useless. It needn't be permitted by the feature. It shouldn't
be permitted by the feature's definition. Until that aspect
of the features definition is removed, other methods
described in this thread remain superior.

These errors could be
entirely eliminated by removing the wierd, indirect, on-
the-fly behavior of VFEs.

Or by not using them this way; it's not something that
people actually want.

It's certainly not something *I* want. That's why I support
removing the capability altogether. As I've *repeatedly*
said: if this and a few other failings were altered, I would
even support the feature for standardization. But, the
feature as *usually* defined will, I hope, never be standardized.

--
J. Giles

"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare


.



Relevant Pages

  • Re: Numeric literals in other than base 10 - was Annoying octal notation
    ... If you want your data file to have values entered in hex, or oct, or even ... able to choose to prepare the data in a certain format - the format ... When designing a language feature don't be too ready to ... impossible or unreasonable to support a feature then by all means ...
    (comp.lang.python)
  • Re: Question about blitting from RGB surface to YUV surface
    ... so if a spec doesnt ask for a feature, the hw guy wont think to add it, ... That and YUV is typically seen as a video format and not a 3D format. ... conversion needed, I should do the work programmly. ... PC with ATI graphic card, I notice that a RGB-format overlay surface was ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Variable length/precision formats?
    ... they do NOT require modification of the format. ... The only fool here is YOU, ... I have implemented the feature. ... in any of the VFEs in the format string gets changed. ...
    (comp.lang.fortran)
  • Re: Excel can automatically put in formulas...or not?!
    ... It is called Extend data range format and formulas, ... In some circumstances, when I type input into a column in a new row, Excel ... Does this feature have a name that I could use to look-up in Help? ...
    (microsoft.public.excel.misc)
  • Re: Removing password-protected
    ... using the Help button in the warning box to which you refer ... format would therefore not show any such shading when reopened. ... then that feature is preserved. ...
    (microsoft.public.project)