The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

dpawson (54) [Avatar] Offline
#1
Parsing a query expression is the act of turning a user-entered textual query such as “mock OR junit” into an appropriate Query object instance

Listing 3.2 shows

Query query = parser.parse("+JUNIT +ANT -MOCK");

You say it's an example, but the term 'MOCK' is not mentioned in the text.
mike.mccandless (221) [Avatar] Offline
#2
Re: pdf p98 99, query string, ref to listing 3.2
Listing 3.2 also includes the query "mock OR junit" (at least in my current iteration on the manuscript)?

Or maybe I don't understand the issue...? Which "text" are you referring to when you say "..., but the term 'MOCK' is not mentioned in the text"?
dpawson (54) [Avatar] Offline
#3
Re: pdf p98 99, query string, ref to listing 3.2
para 3.1.2 says "Parsing a query expression is the act of turning a user-entered textual query such as “mock OR junit”"

the code of listing 3.2 uses

parser.parse("+JUNIT +ANT -MOCK");

IHMO it would make sense if these two were the same.
mike.mccandless (221) [Avatar] Offline
#4
Re: pdf p98 99, query string, ref to listing 3.2
I think I've already fixed this locally in the manuscript -- Listing 3.2 in my current copy has both +JUNIT +ANT -MOCK and mock OR junit examples.