Fowl used in a sentence

Fowl in a sentence as a noun

Don't live/eat/sleep in close proximity to fowl pens.

Anyone know what im talking about.. Smokey smell, looks like a fowl in its cooked form.

I am not denying the possibility that there was fowl play.

You can buy smiling rocks and fart scented candles in stores, and nobody cries fowl.

Instead, the reviewer came to the conclusion that it was more of a "neither fish nor fowl" product.

"Windows RT tablets have a lot of the same neither-fish-nor-fowl nature.

You can see this in sharp relief in the market failure of the ARM-based, neither-fish-nor-fowl Surface.

Basically, you fall fowl of some web-admin and that's you banned for life with absolutely no come back what so ever.

This thread alone should be an example of how irrational some folks are, crying fowl at Google for not wanting brickware in their store.

Fowl in a sentence as a verb

It's been dead for years; the zombie Finder that Apple currently ships is a hideous, mutant hybrid, neither Workspace fish nor Finder fowl.

Fairly sure I remember the Archer guys pointing out some of the code they wanted to put up on the show needed quite a bit of checking to make sure there's no IP fowl ups. Including the output from the program, it can still need correct licencing.

If Microsoft was the company involved everyone would be crying fowl about how they are a monopoly and this is the ultimate evil.

Why not actually have good unit tests and good integration tests, instead of beasts that are neither fish nor fowl and are less than optimal as either?I wonder this myself.

Consider the vast majority of fowl who carry the virus asymptomatically.

[2] The team knows what a contractor is, and they know what a full-fledged fellow employee is, but the arrival of someone who is neither fish nor fowl tends to sow hesitancy and suspicion.

Apple supporters would tirelessly explain that turning MacOS into a commodity OS would make it neither fish nor fowl: It wouldnt have the reach of Windows nor would it have the seamless integration of an Apple-only product.

Why not actually have good unit tests and good integration tests, instead of beasts that are neither fish nor fowl and are less than optimal as either?It seems that the argument here is based on the false dichotomy that suggests if I do unit testing, I can't have integration tests, so I either need to just do integration tests or, for some reason, trade both for some sort-of-unit-ish tests that test the persistence and domain layers as if they were the same unit.