Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I think isprintf is missing from the Printf module of the stdlib #6286

Closed
vicuna opened this issue Jan 6, 2014 · 3 comments
Closed

I think isprintf is missing from the Printf module of the stdlib #6286

vicuna opened this issue Jan 6, 2014 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Jan 6, 2014

Original bug ID: 6286
Reporter: berenger
Status: acknowledged (set by @damiendoligez on 2014-07-16T12:51:53Z)
Resolution: open
Priority: normal
Severity: feature
Category: standard library
Tags: patch, junior_job
Related to: #6017
Monitored by: @gasche @ygrek

Bug description

For the sake of completeness, several printers in the
Printf module don't have an i-equivalent
(that does not print anything but is useful to ignore some material when conditionally printing).

While working on a lazy logger, I was in need of the isprintf.

File attachments

@vicuna
Copy link
Author

vicuna commented Jun 22, 2014

Comment author: fabien

Here is a patch for the module printf and the module format.

Some remaining points:

  • I didn't know what "@SInCE version" I should put in the mli
  • I didn't add i-equivalent functions for the deprecated ones in format
  • I didn't add tests in tformat because the only one present was for the deprecated bprintf
  • how should printf behave with malformed format ?

@vicuna
Copy link
Author

vicuna commented Jun 23, 2014

Comment author: fabien

I've attached a new patch that contains more tests (ibprintf) (the former one can be deleted).
I did not add tests for the continuation printf because I don't know what to do.
Any suggestions would be welcome.

Edit: Please use printf_more_tests2

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant