Welcome, Guest. Please login or register. Did you miss your activation email?
Pages: [1]

Author Topic: Why InputSoundFile::openForWriting?  (Read 2860 times)

0 Members and 1 Guest are viewing this topic.

Jebbs

  • Sr. Member
  • ****
  • Posts: 358
  • DSFML Developer
    • View Profile
    • Email
Why InputSoundFile::openForWriting?
« on: August 05, 2017, 07:24:11 pm »
Why does openForWriting exist in the InputSoundFile header? It seems to be a leftover from SoundFile and has no definition in the cpp file. InputSoundFile should provide read-only access to the file anyway, so this is a weird method to have.

Can it be gotten rid of?
Logged
DSFML - SFML for the D Programming Language.

eXpl0it3r

  • SFML Team
  • Hero Member
  • *****
  • Posts: 10815
    • View Profile
    • development blog
    • Email
Re: Why InputSoundFile::openForWriting?
« Reply #1 on: August 05, 2017, 08:10:47 pm »
This does seem odd indeed and I don't think it was used with libsndfile. Laurent wrote it, so maybe he's some vague memory what he was trying to do here. ;)
Logged
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
——————————————————————
Dev Blog: https://duerrenberger.dev/blog/

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32504
    • View Profile
    • SFML's website
    • Email
Re: Why InputSoundFile::openForWriting?
« Reply #2 on: August 05, 2017, 09:31:11 pm »
If it's not defined, and not used, then it's clearly a leftover and can safely be removed.
Logged
Laurent Gomila - SFML developer
Pages: [1]