The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
there are currently no transformations in there that filter, but it could. I just don't know what you would filter. If there was a reason, then yes, one of these pipe operations would filter, but what they usually do is transform data from one form to another. (from a parser spec to a code file for example)
It works as a pipeline of transformations essentially. Imagine XSLT except not, and you could pipe them together.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
My question is somewhat religious and definitely mundane compared to the guy who wants to write an OS in .net, but I live in the world of maintenance code. My bugaboo is consistency. Take a project of veteran developers (they each have their own style) add a few whiz kids (who have their own styles), add code standards that are pretty much ignored, and shake. The results can be mind-boggling. I've seen coding conventions deal with many issues, but I don't think I've seen one dealing with filenames and their construction. In the project I am re-factoring now, the file system is fixed. The primary folders in the root are fixed, so we have something like:
I have a lot of code that builds file specifications including folder names. A great deal of concatenation, removing slashes, adding slashes and what not, it just begs for errors. So instead of something like this: