Prog2 | Exercícios propostos/projetos nas aulas de Programação | Network Attached Storage library

Here's the solution in Spark:

[namespace.udir]/2 A using-directive specifies that the names in the nominated namespace can be used in the scope in which the using-directive appears after the using-directive. During unqualified name lookup (6.4.1), the names appear as if they were declared in the nearest enclosing namespace which contains both the using-directive and the nominated namespace. [ Note: In this context, “contains” means “contains directly or indirectly”. —end note ]

Emphasis mine. In prog1, that nearest enclosing namespace is the global namespace, and A::Detail is found before ::Detail. In prog2, that nearest enclosing namespace is A, and so the name lookup finds two different namespaces both named A::Detail.

This really isn't a bash question. This is a C++ question really. prog2 should be reading from stdin as jordanm suggested in the comments. Something like this will read from stdin line by line:

There are different ways to tackle this, but something like this should work for your example:

I couldn't find the header vis.h

The author appears to be using this vis function.

Try changing #include to #include .

On my system, this file comes from libbsd-dev package. It is likely that you'll need to link against libbsd.so to get the definition of vis.

I'm assuming that you are using Ansi version of Inno Setup.

In the Ansi version, the culprit is probably the StringChange as it does not play nicely with non-Ansi character sets. Try using StringChangeEx.

Though you should be using Unicode version of Inno Setup anyway.

Only the most recent version of Inno Setup, 5.6, does support Unicode string literals. So make sure you have the latest version.

If you are stuck with an older version:

• Encode the string like

Is this the actual makefile you're using? Because you've not defined either the variable PROG1 or the variable PROG2, so if your makefile looks like that that's clearly the problem.

However, even if you fix that this is dangerous. You should not put both types of objects into the same subdirectory. You'll have to remember to always do a make clean when switching between them because make has no way to know if the previous build used the MATRIX or QTREE settings and you'll be trying to link object files compiled with different settings.

You should create two different OBJ directories, one for each, and use them when building that program.

Marking all as .PHONY means that the target will always be considered dirty and its recipe will be re-evaluated. If you don't want that, move the two programs into explicit targets:

Try this:

1. Remove carriage return from each processes output. Sometimes you may need to substitute carriage return character for a newline. If color is not important, you can just cat -v it.
2. Force line buffering. (This is really only (maybe) needed for the last program in the pipe, but it helps me debugging).